Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4f0c1357d57c5fe9ebb21fc3a303b85ffeb88946e6788c977a540bd48faafbc6

Tx prefix hash: ee125cc3c2a51e20839b171809f12d499e88b8b45c0cb9c42f6180356d9ce0c5
Tx public key: 6b3ed703a5a95d85b6fdf66bcc631e042369b33360cbccb4f82205d513158a40
Timestamp: 1711821511 Timestamp [UTC]: 2024-03-30 17:58:31 Age [y:d:h:m:s]: 02:234:00:49:32
Block: 989775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 692308 RingCT/type: yes/0
Extra: 016b3ed703a5a95d85b6fdf66bcc631e042369b33360cbccb4f82205d513158a400211000000060011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b185e4e0fedfc39162f612ecc29d74db7d106a6e505e727f23b25367a0f51ff1 0.000600000000 1450093 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 989785, "vin": [ { "gen": { "height": 989775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b185e4e0fedfc39162f612ecc29d74db7d106a6e505e727f23b25367a0f51ff1" } } ], "extra": [ 1, 107, 62, 215, 3, 165, 169, 93, 133, 182, 253, 246, 107, 204, 99, 30, 4, 35, 105, 179, 51, 96, 203, 204, 180, 248, 34, 5, 213, 19, 21, 138, 64, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: