Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d87e56a0037b9d1ab15c2db37d28921caa1adb2a503853dd09714d5247196d67

Tx prefix hash: 211976dcd1d920b7aa067ae6c3968cac36a02cad1c61d080e9c268074a07b187
Tx public key: c4000bbfdef96623b177908d6f956e1ece18c0482dd83678ed1fb062d33e81f6
Timestamp: 1702542821 Timestamp [UCT]: 2023-12-14 08:33:41 Age [y:d:h:m:s]: 01:037:08:37:22
Block: 912823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288027 RingCT/type: yes/0
Extra: 01c4000bbfdef96623b177908d6f956e1ece18c0482dd83678ed1fb062d33e81f6021100000008faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00694c9ab6930e0241e636b3dd1ca1803241f16e8c2f47bc7d9eb769e87d8e1f 0.600000000000 1370059 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": 912833, "vin": [ { "gen": { "height": 912823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00694c9ab6930e0241e636b3dd1ca1803241f16e8c2f47bc7d9eb769e87d8e1f" } } ], "extra": [ 1, 196, 0, 11, 191, 222, 249, 102, 35, 177, 119, 144, 141, 111, 149, 110, 30, 206, 24, 192, 72, 45, 216, 54, 120, 237, 31, 176, 98, 211, 62, 129, 246, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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