Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51cd8cbe144f1f6fc331acd4597f7c8a2b0243d8d8690226032d9813f81f40ae

Tx prefix hash: 3ce581843d6a73148a1830224144428b7ed7e94e9b602df6148b8ce5192ffe35
Tx public key: 0e3e80a1e4524fae71bd0a438ade4658643096ceac0d60bf09f4d3f108c72d8a
Timestamp: 1747772954 Timestamp [UCT]: 2025-05-20 20:29:14 Age [y:d:h:m:s]: 00:229:05:03:11
Block: 1287280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161576 RingCT/type: yes/0
Extra: 010e3e80a1e4524fae71bd0a438ade4658643096ceac0d60bf09f4d3f108c72d8a0211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2b47de3b670395635f36a9e4be08dc15dc1643e35cbcd2cc7d56c7e96f6bf83 0.600000000000 1774747 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": 1287290, "vin": [ { "gen": { "height": 1287280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2b47de3b670395635f36a9e4be08dc15dc1643e35cbcd2cc7d56c7e96f6bf83" } } ], "extra": [ 1, 14, 62, 128, 161, 228, 82, 79, 174, 113, 189, 10, 67, 138, 222, 70, 88, 100, 48, 150, 206, 172, 13, 96, 191, 9, 244, 211, 241, 8, 199, 45, 138, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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