Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d7fa68a9e0da6a8029203e1d64fcec4451360e516f819e5a014fc6976ecf98b

Tx prefix hash: 4e8d8a394d311593917baf08f3a0a36179f5be466853fe2aef33682aa400f7fa
Tx public key: 72d98037f2e7973491fe776e6d9bac168b9ffe12cb680dc9d607608e36a8ffc2
Timestamp: 1735089351 Timestamp [UCT]: 2024-12-25 01:15:51 Age [y:d:h:m:s]: 00:125:02:25:33
Block: 1182540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89217 RingCT/type: yes/0
Extra: 0172d98037f2e7973491fe776e6d9bac168b9ffe12cb680dc9d607608e36a8ffc20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fcfd09c210d4ba5c3ad3ad2a19b2f85bf0d0378b1856a8ac32e1d08fb6e34c2 0.600000000000 1668975 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": 1182550, "vin": [ { "gen": { "height": 1182540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fcfd09c210d4ba5c3ad3ad2a19b2f85bf0d0378b1856a8ac32e1d08fb6e34c2" } } ], "extra": [ 1, 114, 217, 128, 55, 242, 231, 151, 52, 145, 254, 119, 110, 109, 155, 172, 22, 139, 159, 254, 18, 203, 104, 13, 201, 214, 7, 96, 142, 54, 168, 255, 194, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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