Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cad20ca361203c1f88d1cf9ccca8bd1eef624e2ce04e32c97c3026961abd6fe

Tx prefix hash: dd60cd35bf9c33e95040851eb32b0628fc82f1f2793640829aa86afefb30ff12
Tx public key: 1f371092ba24d0116226c57449a8b084b4ea2d8415388f43090497afe7d359f6
Timestamp: 1578791215 Timestamp [UCT]: 2020-01-12 01:06:55 Age [y:d:h:m:s]: 04:320:10:40:51
Block: 43556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118542 RingCT/type: yes/0
Extra: 011f371092ba24d0116226c57449a8b084b4ea2d8415388f43090497afe7d359f602110000001e4ac5aa02000000000000000000

1 output(s) for total of 440.232127414000 dcy

stealth address amount amount idx
00: 8b061a7882cd5398ee6aae5bb02a0fb83417d9dccb98317d68dc1358f5a5e5b0 440.232127414000 78940 of 0

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": 43566, "vin": [ { "gen": { "height": 43556 } } ], "vout": [ { "amount": 440232127414, "target": { "key": "8b061a7882cd5398ee6aae5bb02a0fb83417d9dccb98317d68dc1358f5a5e5b0" } } ], "extra": [ 1, 31, 55, 16, 146, 186, 36, 208, 17, 98, 38, 197, 116, 73, 168, 176, 132, 180, 234, 45, 132, 21, 56, 143, 67, 9, 4, 151, 175, 231, 211, 89, 246, 2, 17, 0, 0, 0, 30, 74, 197, 170, 2, 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