Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b920a6b71d67936b379c0f951464175b37fea7c287905461bb805da99b7870f

Tx prefix hash: 56f05d1b0de6f4102cc314b61f46172ce486c6576fe2488d51d9ad407cab006e
Tx public key: 2afbb752916debe3a82d33e69c9e83d9e228f87fa4605b7d16cfcc64d5dd3cb5
Timestamp: 1687775729 Timestamp [UCT]: 2023-06-26 10:35:29 Age [y:d:h:m:s]: 01:288:09:19:04
Block: 790666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467251 RingCT/type: yes/0
Extra: 012afbb752916debe3a82d33e69c9e83d9e228f87fa4605b7d16cfcc64d5dd3cb50211000000017e406890000000000000000000

1 output(s) for total of 1.472975301000 dcy

stealth address amount amount idx
00: 8deb5900599d1f9547adcc714e2253a7f71f2ca56fa11bcefcb27a8c45503c3e 1.472975301000 1241061 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": 790676, "vin": [ { "gen": { "height": 790666 } } ], "vout": [ { "amount": 1472975301, "target": { "key": "8deb5900599d1f9547adcc714e2253a7f71f2ca56fa11bcefcb27a8c45503c3e" } } ], "extra": [ 1, 42, 251, 183, 82, 145, 109, 235, 227, 168, 45, 51, 230, 156, 158, 131, 217, 226, 40, 248, 127, 164, 96, 91, 125, 22, 207, 204, 100, 213, 221, 60, 181, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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