Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba3da7c66549f5f2e3c274e58bab85916ed1cf7df26dcbd37a2869e3fbfa995c

Tx prefix hash: 601ba57fb8aebac84363b66142184de8a9dc382953a12f472ee994a93f4c50af
Tx public key: e43d8ee875b8b2e302853e6f6c2d8f253dc064ba72a14f13d560598e05cf4578
Timestamp: 1743810177 Timestamp [UTC]: 2025-04-04 23:42:57 Age [y:d:h:m:s]: 01:226:15:12:54
Block: 1254456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425996 RingCT/type: yes/0
Extra: 01e43d8ee875b8b2e302853e6f6c2d8f253dc064ba72a14f13d560598e05cf45780211000000064060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1cffdcaf628b3c18ed8801a8a44100c5990b741527da97c7841e76b3a8e94d90 0.000600000000 1741537 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": 1254466, "vin": [ { "gen": { "height": 1254456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cffdcaf628b3c18ed8801a8a44100c5990b741527da97c7841e76b3a8e94d90" } } ], "extra": [ 1, 228, 61, 142, 232, 117, 184, 178, 227, 2, 133, 62, 111, 108, 45, 143, 37, 61, 192, 100, 186, 114, 161, 79, 19, 213, 96, 89, 142, 5, 207, 69, 120, 2, 17, 0, 0, 0, 6, 64, 96, 246, 210, 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: