Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 073afeea9e6acbc4dd821dc831fbc608956914c46bc7b07be0aaa97d5f6bdec1

Tx prefix hash: 38a2ff4d77c76960d73443279c5d442ac7ff797245e293d24472a1521ad8d6b5
Tx public key: 0c418d68351b95be203c9adc4bc1bbcbd1147035fe0d4b4a28b5f7102f371593
Timestamp: 1708294350 Timestamp [UCT]: 2024-02-18 22:12:30 Age [y:d:h:m:s]: 01:072:07:48:41
Block: 960516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312718 RingCT/type: yes/0
Extra: 010c418d68351b95be203c9adc4bc1bbcbd1147035fe0d4b4a28b5f7102f3715930211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aab84cb573d00016785a7721fa6a2cf877d8cb6a37d7cb866e49345a69f378f1 0.600000000000 1420087 of 15

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": 960526, "vin": [ { "gen": { "height": 960516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aab84cb573d00016785a7721fa6a2cf877d8cb6a37d7cb866e49345a69f378f1" } } ], "extra": [ 1, 12, 65, 141, 104, 53, 27, 149, 190, 32, 60, 154, 220, 75, 193, 187, 203, 209, 20, 112, 53, 254, 13, 75, 74, 40, 181, 247, 16, 47, 55, 21, 147, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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