Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1e543207f1a9eba20cc8518ce00f7d04785235d7d74b6aa4a6dbedcd33b04c9

Tx prefix hash: d6350a49d5e7d6ceb80ce524d037fdeb831fe1edb1a3448abed4953587efc951
Tx public key: 5ed052504cbcff8383159923a2e13e2b8303e25c0ae4f123fbf0f1e5552ddf3c
Timestamp: 1739005610 Timestamp [UTC]: 2025-02-08 09:06:50 Age [y:d:h:m:s]: 01:282:17:19:32
Block: 1214686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466125 RingCT/type: yes/0
Extra: 015ed052504cbcff8383159923a2e13e2b8303e25c0ae4f123fbf0f1e5552ddf3c0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ecb5c622d852ce41e746447251f77331e94a58639b033bf3daa1374dcda32ea6 0.000600000000 1701481 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": 1214696, "vin": [ { "gen": { "height": 1214686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecb5c622d852ce41e746447251f77331e94a58639b033bf3daa1374dcda32ea6" } } ], "extra": [ 1, 94, 208, 82, 80, 76, 188, 255, 131, 131, 21, 153, 35, 162, 225, 62, 43, 131, 3, 226, 92, 10, 228, 241, 35, 251, 240, 241, 229, 85, 45, 223, 60, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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: