Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 298ace3e58f0f4c61859d5b579a58ed2e6eeee209fc6f3f9d5778ce9d97d822f

Tx prefix hash: 6de3e7548eb5d145c367d2522598bdbda1192214baabea739bdee23b38f62313
Tx public key: 85c162f4d8d30e6304fa809bd67eaafe8a14504154c9e3cde9c967ad16d12187
Timestamp: 1750804268 Timestamp [UTC]: 2025-06-24 22:31:08 Age [y:d:h:m:s]: 00:320:02:46:14
Block: 1312103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219426 RingCT/type: yes/0
Extra: 0185c162f4d8d30e6304fa809bd67eaafe8a14504154c9e3cde9c967ad16d12187021100000004d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2bed38e2caa967b1f69799dab65cecbafec110a22cdc006af0ac38fcdbc43439 0.000600000000 1799734 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": 1312113, "vin": [ { "gen": { "height": 1312103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bed38e2caa967b1f69799dab65cecbafec110a22cdc006af0ac38fcdbc43439" } } ], "extra": [ 1, 133, 193, 98, 244, 216, 211, 14, 99, 4, 250, 128, 155, 214, 126, 170, 254, 138, 20, 80, 65, 84, 201, 227, 205, 233, 201, 103, 173, 22, 209, 33, 135, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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: