Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 778cb42bdb4701c1800bec73aead2b7e0ceb3dfe3745a4e3aef1fee69d04cbce

Tx prefix hash: 0cca23544031bd9d669841032cdf78fc7af82f40e6864c83b876f0adbbc0c1ee
Tx public key: 0dfd376eeae5503bf6054b6e2c51533e3ab1cb964c72742bcfe34acaabc0a0f4
Timestamp: 1667149134 Timestamp [UCT]: 2022-10-30 16:58:54 Age [y:d:h:m:s]: 02:211:11:08:10
Block: 620380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 672850 RingCT/type: yes/0
Extra: 010dfd376eeae5503bf6054b6e2c51533e3ab1cb964c72742bcfe34acaabc0a0f402110000000283600029000000000000000000

1 output(s) for total of 5.400370521000 dcy

stealth address amount amount idx
00: ba3ad8239329c49d09e341c471df1226b005ed0017cb12147ef013ce257475af 5.400370521000 1058253 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": 620390, "vin": [ { "gen": { "height": 620380 } } ], "vout": [ { "amount": 5400370521, "target": { "key": "ba3ad8239329c49d09e341c471df1226b005ed0017cb12147ef013ce257475af" } } ], "extra": [ 1, 13, 253, 55, 110, 234, 229, 80, 59, 246, 5, 75, 110, 44, 81, 83, 62, 58, 177, 203, 150, 76, 114, 116, 43, 207, 227, 74, 202, 171, 192, 160, 244, 2, 17, 0, 0, 0, 2, 131, 96, 0, 41, 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