Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23da1c76e3bd9b339e45dd43780a73ee855db7628e943b603815a5794795c63a

Tx prefix hash: cda752e804116a8339271e607681d8f44380976a806fb75278855085520b23a0
Tx public key: 20f30c80fe59c093602806c38f37b69398451129b3e8e2f40e437c64dfb414a7
Timestamp: 1710753682 Timestamp [UCT]: 2024-03-18 09:21:22 Age [y:d:h:m:s]: 01:089:03:05:12
Block: 980921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324606 RingCT/type: yes/0
Extra: 0120f30c80fe59c093602806c38f37b69398451129b3e8e2f40e437c64dfb414a702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75f0d7ff3cdfb11d36c8d8a9e77a7858f5051da0c11e74d81b6e54b5ae92a32b 0.600000000000 1441006 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": 980931, "vin": [ { "gen": { "height": 980921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75f0d7ff3cdfb11d36c8d8a9e77a7858f5051da0c11e74d81b6e54b5ae92a32b" } } ], "extra": [ 1, 32, 243, 12, 128, 254, 89, 192, 147, 96, 40, 6, 195, 143, 55, 182, 147, 152, 69, 17, 41, 179, 232, 226, 244, 14, 67, 124, 100, 223, 180, 20, 167, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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