Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aef68cf54e51ec02d7df1f52c80bebf2b49e51520663ff8a5cdae20f7cdecf2f

Tx prefix hash: 99cb020b8d8b151ff88c5fcd09b6e0d84d462c39343a64d54ef2ba4197196ace
Tx public key: c6dd76cc8c7797d7df25cc3431abf8b036994c3b7d9c9cd2e41a73e193c1b59a
Timestamp: 1734925389 Timestamp [UCT]: 2024-12-23 03:43:09 Age [y:d:h:m:s]: 00:127:17:16:33
Block: 1181205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91064 RingCT/type: yes/0
Extra: 01c6dd76cc8c7797d7df25cc3431abf8b036994c3b7d9c9cd2e41a73e193c1b59a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96f5923c33a3ab100a89fb7b0efd908fe6de37d4bda19414d9434ca5f7aa76e2 0.600000000000 1667622 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": 1181215, "vin": [ { "gen": { "height": 1181205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96f5923c33a3ab100a89fb7b0efd908fe6de37d4bda19414d9434ca5f7aa76e2" } } ], "extra": [ 1, 198, 221, 118, 204, 140, 119, 151, 215, 223, 37, 204, 52, 49, 171, 248, 176, 54, 153, 76, 59, 125, 156, 156, 210, 228, 26, 115, 225, 147, 193, 181, 154, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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