Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63c73ba69953faae1c194276a92ea96d9c8fe2703a17281fddd85290a81aa88b

Tx prefix hash: 3cc8198f62256c2031161df835a0bff588f357c7192cfa6cd492af77d3363dbd
Tx public key: 83896fbacee4e5c512ab3fee39d58b704559f3a2c1633c972a0950474903b14c
Timestamp: 1660007351 Timestamp [UCT]: 2022-08-09 01:09:11 Age [y:d:h:m:s]: 02:203:11:32:53
Block: 561760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 666622 RingCT/type: yes/0
Extra: 0183896fbacee4e5c512ab3fee39d58b704559f3a2c1633c972a0950474903b14c0211000000026570b1ef000000000000000000

1 output(s) for total of 8.446096466000 dcy

stealth address amount amount idx
00: 176955ea2f2d3a52007eb3a9e4fe3ecacc3ba4a0f4113fe0b7d48782a83eaeb8 8.446096466000 994244 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": 561770, "vin": [ { "gen": { "height": 561760 } } ], "vout": [ { "amount": 8446096466, "target": { "key": "176955ea2f2d3a52007eb3a9e4fe3ecacc3ba4a0f4113fe0b7d48782a83eaeb8" } } ], "extra": [ 1, 131, 137, 111, 186, 206, 228, 229, 197, 18, 171, 63, 238, 57, 213, 139, 112, 69, 89, 243, 162, 193, 99, 60, 151, 42, 9, 80, 71, 73, 3, 177, 76, 2, 17, 0, 0, 0, 2, 101, 112, 177, 239, 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