Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5195a1541d3a3cf98b5cf9df8ad3f5b349cb7142ceccc7fd1d917b686a79b87c

Tx prefix hash: f9203b130723aeab441808e49036bfdc58b77b8e9cad75540b83287a40874a57
Tx public key: 7a94857ecb2944bdc08683900e34d82cb3b3dbabb679372e3dd8c9e3a7d77390
Timestamp: 1734857287 Timestamp [UCT]: 2024-12-22 08:48:07 Age [y:d:h:m:s]: 00:103:20:22:45
Block: 1180642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73971 RingCT/type: yes/0
Extra: 017a94857ecb2944bdc08683900e34d82cb3b3dbabb679372e3dd8c9e3a7d773900211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c83c488007a916b31c9f8292de9ff7be79fd12680b30fcee7e13bbb832ea8785 0.600000000000 1667055 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": 1180652, "vin": [ { "gen": { "height": 1180642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c83c488007a916b31c9f8292de9ff7be79fd12680b30fcee7e13bbb832ea8785" } } ], "extra": [ 1, 122, 148, 133, 126, 203, 41, 68, 189, 192, 134, 131, 144, 14, 52, 216, 44, 179, 179, 219, 171, 182, 121, 55, 46, 61, 216, 201, 227, 167, 215, 115, 144, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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