Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bfd122649a13d1b475f07a7d0d64aa91f1f29ce484366bed263d26de7071122

Tx prefix hash: ba56ada5acf801a8ea5485ca779bd3eb25a4ebe0dfaa334a18bb1ab33af4958a
Tx public key: eb825470d3f18d2fd4e9dbb87ea38f9c9d525369abe25a03f6e15b92f2158e6a
Timestamp: 1630361258 Timestamp [UCT]: 2021-08-30 22:07:38 Age [y:d:h:m:s]: 03:120:10:17:22
Block: 324123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 860768 RingCT/type: yes/0
Extra: 01eb825470d3f18d2fd4e9dbb87ea38f9c9d525369abe25a03f6e15b92f2158e6a021100000019a272b9cb000000000000000000

1 output(s) for total of 51.766214349000 dcy

stealth address amount amount idx
00: 6a1ea76b9a065f7076e7cb3c9188b584de9d3353dc20bdf0f73549bc8e2229ca 51.766214349000 672122 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": 324133, "vin": [ { "gen": { "height": 324123 } } ], "vout": [ { "amount": 51766214349, "target": { "key": "6a1ea76b9a065f7076e7cb3c9188b584de9d3353dc20bdf0f73549bc8e2229ca" } } ], "extra": [ 1, 235, 130, 84, 112, 211, 241, 141, 47, 212, 233, 219, 184, 126, 163, 143, 156, 157, 82, 83, 105, 171, 226, 90, 3, 246, 225, 91, 146, 242, 21, 142, 106, 2, 17, 0, 0, 0, 25, 162, 114, 185, 203, 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