Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6f010cede83ffe2e9e9cbfdc032c96e38d368546dee945390aa6581ccd15b37

Tx prefix hash: 23b26e2fa9cb739ba3a41853a6615c7e1813933a41138c39ae661fd7a502bb2b
Tx public key: d66200038f6cbf040222e46922600c92bf9efb602d2e4ad1cbf9bc385951bf17
Timestamp: 1742109824 Timestamp [UTC]: 2025-03-16 07:23:44 Age [y:d:h:m:s]: 00:360:19:12:31
Block: 1240403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255514 RingCT/type: yes/0
Extra: 01d66200038f6cbf040222e46922600c92bf9efb602d2e4ad1cbf9bc385951bf170211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b9ec6d9d646886727b3dee48dc2224072c3c678f725e51c42faed99295afdbd3 0.000600000000 1727368 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": 1240413, "vin": [ { "gen": { "height": 1240403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9ec6d9d646886727b3dee48dc2224072c3c678f725e51c42faed99295afdbd3" } } ], "extra": [ 1, 214, 98, 0, 3, 143, 108, 191, 4, 2, 34, 228, 105, 34, 96, 12, 146, 191, 158, 251, 96, 45, 46, 74, 209, 203, 249, 188, 56, 89, 81, 191, 23, 2, 17, 0, 0, 0, 4, 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) | dinastycoin version: tesla-369