Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f56c82b8606115b792ef63d0cdc74de86d99142fdead31f5c4216c93e176a3c5

Tx prefix hash: d84e1861e4e46a3090ce885dda83a9b2ba532d43e40f5f453cf20203e2d1d705
Tx public key: 2a69477ee8d36d8e7834649a0a594305f753bba591a6d70f6c59d76d84e3ce58
Timestamp: 1713393376 Timestamp [UCT]: 2024-04-17 22:36:16 Age [y:d:h:m:s]: 01:244:02:56:44
Block: 1002770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433189 RingCT/type: yes/0
Extra: 012a69477ee8d36d8e7834649a0a594305f753bba591a6d70f6c59d76d84e3ce5802110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c803d72ac293eb4a8ec056b09e17788ef2f7d465b084473d5c2729e9843072b8 0.600000000000 1463292 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": 1002780, "vin": [ { "gen": { "height": 1002770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c803d72ac293eb4a8ec056b09e17788ef2f7d465b084473d5c2729e9843072b8" } } ], "extra": [ 1, 42, 105, 71, 126, 232, 211, 109, 142, 120, 52, 100, 154, 10, 89, 67, 5, 247, 83, 187, 165, 145, 166, 215, 15, 108, 89, 215, 109, 132, 227, 206, 88, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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