Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2f72add2939c420b8fe034bb5782d06b511e7f70f5ba88e43ea26032f836466

Tx prefix hash: bc1297f561d0500cfaccc8b637bb259c3d9716569e915f9333b88bcd0e91977e
Tx public key: 8dbe468313b631e88043598f5998f1af9c192cc4461e7e2821d04b45d3583794
Timestamp: 1575875660 Timestamp [UCT]: 2019-12-09 07:14:20 Age [y:d:h:m:s]: 05:075:07:12:53
Block: 23677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1199730 RingCT/type: yes/0
Extra: 018dbe468313b631e88043598f5998f1af9c192cc4461e7e2821d04b45d3583794021100000011ad433a0b000000000000000000

1 output(s) for total of 512.329238617000 dcy

stealth address amount amount idx
00: 7478b57a6748ea3338e1e57d29cc2f6626096b1f07a797f4dd5930351b6aa5f0 512.329238617000 38406 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": 23687, "vin": [ { "gen": { "height": 23677 } } ], "vout": [ { "amount": 512329238617, "target": { "key": "7478b57a6748ea3338e1e57d29cc2f6626096b1f07a797f4dd5930351b6aa5f0" } } ], "extra": [ 1, 141, 190, 70, 131, 19, 182, 49, 232, 128, 67, 89, 143, 89, 152, 241, 175, 156, 25, 44, 196, 70, 30, 126, 40, 33, 208, 75, 69, 211, 88, 55, 148, 2, 17, 0, 0, 0, 17, 173, 67, 58, 11, 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