Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92fdea84314b1a00799aaa0fa21ada44d1272f39b5f8d0a286271ed0bf981c48

Tx prefix hash: 080ca17062a9cbe60b702c931fbdd3c5b5202e746648f1fb90ca2822634d5cce
Tx public key: 9e8b882f40688df56a79502e0619063a021191d4d1ebfab2e5fe54f6009b8112
Timestamp: 1720165021 Timestamp [UCT]: 2024-07-05 07:37:01 Age [y:d:h:m:s]: 00:313:20:12:47
Block: 1058915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224276 RingCT/type: yes/0
Extra: 019e8b882f40688df56a79502e0619063a021191d4d1ebfab2e5fe54f6009b811202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f70bd6f3880e68d4e341d00673e09743d1bf111c585f133d0c7a2dcd09a8bfb 0.600000000000 1529374 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": 1058925, "vin": [ { "gen": { "height": 1058915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f70bd6f3880e68d4e341d00673e09743d1bf111c585f133d0c7a2dcd09a8bfb" } } ], "extra": [ 1, 158, 139, 136, 47, 64, 104, 141, 245, 106, 121, 80, 46, 6, 25, 6, 58, 2, 17, 145, 212, 209, 235, 250, 178, 229, 254, 84, 246, 0, 155, 129, 18, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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