Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a2be09ac24597d22d4f0da2673d819a4b596cb6927fe4509a310f14e98a779c

Tx prefix hash: ed69a76e91b09831982a4a92e56728cd6385d80735faaa4ad9be2fe68278b24e
Tx public key: 82401ab79975ed0d7e1396fde7c6c28ba9c0cd7c1815f07b3d1f4134e198fff9
Timestamp: 1715004251 Timestamp [UCT]: 2024-05-06 14:04:11 Age [y:d:h:m:s]: 00:320:00:56:46
Block: 1016136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228769 RingCT/type: yes/0
Extra: 0182401ab79975ed0d7e1396fde7c6c28ba9c0cd7c1815f07b3d1f4134e198fff90211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 777c37c587d59a85b02f09b7f886fb2a95f88efa2e4cf42db04d3f2818841f25 0.600000000000 1479635 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": 1016146, "vin": [ { "gen": { "height": 1016136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "777c37c587d59a85b02f09b7f886fb2a95f88efa2e4cf42db04d3f2818841f25" } } ], "extra": [ 1, 130, 64, 26, 183, 153, 117, 237, 13, 126, 19, 150, 253, 231, 198, 194, 139, 169, 192, 205, 124, 24, 21, 240, 123, 61, 31, 65, 52, 225, 152, 255, 249, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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