Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 304ba67a8fe9692f8fd7363d1fd3b4b944d74742c0ddc22837a6c23152733bcb

Tx prefix hash: 91ec311118886fb5e1a02ec230c8120ccd96a0407802fb89b06de9fb37995427
Tx public key: efb278a249ef8a58022a2f4ec5598131f236b9b3aa654b96c129313dec35aae2
Timestamp: 1708358628 Timestamp [UCT]: 2024-02-19 16:03:48 Age [y:d:h:m:s]: 01:264:15:28:09
Block: 961035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447901 RingCT/type: yes/0
Extra: 01efb278a249ef8a58022a2f4ec5598131f236b9b3aa654b96c129313dec35aae20211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cea285cba4ed67893e476d35c707923f0df8f91ee2357e4f6af8bd3e6b44e09 0.600000000000 1420622 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": 961045, "vin": [ { "gen": { "height": 961035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cea285cba4ed67893e476d35c707923f0df8f91ee2357e4f6af8bd3e6b44e09" } } ], "extra": [ 1, 239, 178, 120, 162, 73, 239, 138, 88, 2, 42, 47, 78, 197, 89, 129, 49, 242, 54, 185, 179, 170, 101, 75, 150, 193, 41, 49, 61, 236, 53, 170, 226, 2, 17, 0, 0, 0, 8, 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