Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9f891f832436f15169c7de15726005644faea950889b822f281611d10b010f3

Tx prefix hash: eb5e9d8b8189d1b924cbe75f4c3996d499f4360b797ccee5fbd2ad418e1b2199
Tx public key: e12967aac8d066313d6c7fed844911cfe7933f4ce953ff69c98c30f1f263d93c
Timestamp: 1699724352 Timestamp [UCT]: 2023-11-11 17:39:12 Age [y:d:h:m:s]: 01:149:02:29:48
Block: 889456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367750 RingCT/type: yes/0
Extra: 01e12967aac8d066313d6c7fed844911cfe7933f4ce953ff69c98c30f1f263d93c0211000000014b8f5122000000000000000000

1 output(s) for total of 0.693207160000 dcy

stealth address amount amount idx
00: 4866d5e1f376fe5c2a6d150ea04b367b28fc281ad9e3ef5ad54655bd4f2d2ea3 0.693207160000 1345453 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": 889466, "vin": [ { "gen": { "height": 889456 } } ], "vout": [ { "amount": 693207160, "target": { "key": "4866d5e1f376fe5c2a6d150ea04b367b28fc281ad9e3ef5ad54655bd4f2d2ea3" } } ], "extra": [ 1, 225, 41, 103, 170, 200, 208, 102, 49, 61, 108, 127, 237, 132, 73, 17, 207, 231, 147, 63, 76, 233, 83, 255, 105, 201, 140, 48, 241, 242, 99, 217, 60, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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