Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e27d32507e4ec470c1621a89c078de4c1456e6416658387273e9eef36b85600b

Tx prefix hash: 987708105658a16cb34f866a82f2bcd811ff1224d449ea14f7d4f4a5cdbf1de6
Tx public key: 424622b47fbc83a3e7d67cbefd0284b9ca40b28d77f491b7d2b07f720e74cfdf
Timestamp: 1746165620 Timestamp [UCT]: 2025-05-02 06:00:20 Age [y:d:h:m:s]: 00:203:09:03:06
Block: 1273959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143061 RingCT/type: yes/0
Extra: 01424622b47fbc83a3e7d67cbefd0284b9ca40b28d77f491b7d2b07f720e74cfdf02110000000801491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e33deae27c87d811ade8988b248a82848249347b18e79332c5c9a5c5c9cdbdf 0.600000000000 1761246 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": 1273969, "vin": [ { "gen": { "height": 1273959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e33deae27c87d811ade8988b248a82848249347b18e79332c5c9a5c5c9cdbdf" } } ], "extra": [ 1, 66, 70, 34, 180, 127, 188, 131, 163, 231, 214, 124, 190, 253, 2, 132, 185, 202, 64, 178, 141, 119, 244, 145, 183, 210, 176, 127, 114, 14, 116, 207, 223, 2, 17, 0, 0, 0, 8, 1, 73, 31, 136, 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