Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d23d13f663813236fe0401c76e04304ce8101738e6179d3d3e4965498da5e40

Tx prefix hash: f5d1c8a7ffe8800ec7126037f49e1204fb5a0a13fa890d6a4bae30692cdb712b
Tx public key: 14a289a4173b5e341a1f90037c0a6fabfc83cc94a0c280481abcc22b92e5bb35
Timestamp: 1577170397 Timestamp [UCT]: 2019-12-24 06:53:17 Age [y:d:h:m:s]: 05:116:22:59:00
Block: 30463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1233477 RingCT/type: yes/0
Extra: 0114a289a4173b5e341a1f90037c0a6fabfc83cc94a0c280481abcc22b92e5bb35021100000002d81c26c0000000000000000000

1 output(s) for total of 486.479223067000 dcy

stealth address amount amount idx
00: 27293d0507f854629f4b395eb63bc77101a4b678ec2cf55e6afafab1633ee72f 486.479223067000 50301 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": 30473, "vin": [ { "gen": { "height": 30463 } } ], "vout": [ { "amount": 486479223067, "target": { "key": "27293d0507f854629f4b395eb63bc77101a4b678ec2cf55e6afafab1633ee72f" } } ], "extra": [ 1, 20, 162, 137, 164, 23, 59, 94, 52, 26, 31, 144, 3, 124, 10, 111, 171, 252, 131, 204, 148, 160, 194, 128, 72, 26, 188, 194, 43, 146, 229, 187, 53, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 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