Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bc83efd22aaf5a43a1830c3b6a616d5674cc6f0631763e54d1022022d34e4d6

Tx prefix hash: 4a978d86cb1e2e59b19d4a47ebfe8298f3848e0ad438a6bd3af8b32d9ee2bb0b
Tx public key: c863edefba7f931e1b0ee57e9efefbf3de4446fcbdd24532a6a8beaaf8f66a4f
Timestamp: 1624329584 Timestamp [UCT]: 2021-06-22 02:39:44 Age [y:d:h:m:s]: 04:132:18:35:53
Block: 282008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120180 RingCT/type: yes/0
Extra: 01c863edefba7f931e1b0ee57e9efefbf3de4446fcbdd24532a6a8beaaf8f66a4f0211000000053634f08d000000000000000000

1 output(s) for total of 71.385557106000 dcy

stealth address amount amount idx
00: 6dc543b42d86032a56a262cc5494533dd87a6f23a5d3262a6580a8dd83fcee03 71.385557106000 590537 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": 282018, "vin": [ { "gen": { "height": 282008 } } ], "vout": [ { "amount": 71385557106, "target": { "key": "6dc543b42d86032a56a262cc5494533dd87a6f23a5d3262a6580a8dd83fcee03" } } ], "extra": [ 1, 200, 99, 237, 239, 186, 127, 147, 30, 27, 14, 229, 126, 158, 254, 251, 243, 222, 68, 70, 252, 189, 210, 69, 50, 166, 168, 190, 170, 248, 246, 106, 79, 2, 17, 0, 0, 0, 5, 54, 52, 240, 141, 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