Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 862eca6cf4cbe5fe109ec6ca51bfef99e4f9207056e0bab3c37ba91a7b922cef

Tx prefix hash: 9454536e79232ce39e0a4c5aa5a763e4c95b37cdbecc257e836567c50403a81e
Tx public key: b08e1519818f99d7fdce40cf24c8dbb179336735f76d4f7a7d29a4a7e33b8ca4
Timestamp: 1723874527 Timestamp [UCT]: 2024-08-17 06:02:07 Age [y:d:h:m:s]: 00:264:20:33:37
Block: 1089682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189172 RingCT/type: yes/0
Extra: 01b08e1519818f99d7fdce40cf24c8dbb179336735f76d4f7a7d29a4a7e33b8ca4021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4661b45372cdc373119e19048b0e1979efd676439561f6ca8d878e72f3d6ea29 0.600000000000 1564305 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": 1089692, "vin": [ { "gen": { "height": 1089682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4661b45372cdc373119e19048b0e1979efd676439561f6ca8d878e72f3d6ea29" } } ], "extra": [ 1, 176, 142, 21, 25, 129, 143, 153, 215, 253, 206, 64, 207, 36, 200, 219, 177, 121, 51, 103, 53, 247, 109, 79, 122, 125, 41, 164, 167, 227, 59, 140, 164, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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