Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 522c00fda3d6e4a4fee3bc64465afd146da8e74f33a1f29b7c6f5c91ae95ae15

Tx prefix hash: e0fad486c2c72248f318eddaf1757d4aa85f54dc2913763a972cabe59c10393a
Tx public key: b6bfd5b6e2a27a00457a1711f31405e21c176edd8cfd789b02e833ed7657bd4a
Timestamp: 1749670282 Timestamp [UCT]: 2025-06-11 19:31:22 Age [y:d:h:m:s]: 00:162:02:22:29
Block: 1302973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113542 RingCT/type: yes/0
Extra: 01b6bfd5b6e2a27a00457a1711f31405e21c176edd8cfd789b02e833ed7657bd4a02110000001b43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aefc1c18ae0a6797771704390a2fcd7a532833bf83a23cc3597d568534ef71a 0.600000000000 1790548 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 dinasty-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": 1302983, "vin": [ { "gen": { "height": 1302973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aefc1c18ae0a6797771704390a2fcd7a532833bf83a23cc3597d568534ef71a" } } ], "extra": [ 1, 182, 191, 213, 182, 226, 162, 122, 0, 69, 122, 23, 17, 243, 20, 5, 226, 28, 23, 110, 221, 140, 253, 120, 155, 2, 232, 51, 237, 118, 87, 189, 74, 2, 17, 0, 0, 0, 27, 67, 132, 109, 102, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8