Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd780afbd93144f38e91c8b5dded0c71291c6261ad0ed8cd879d3ff8c7c9057e

Tx prefix hash: e50fef616c82126c5e1ccbb604bb4d9ca06cf9322408d51b5d01ff5ea35c6780
Tx public key: bbc777b8553a14ab88e3df45c1fa0ef9b5cef34ef2f356e48315090a945ca60d
Timestamp: 1727365115 Timestamp [UCT]: 2024-09-26 15:38:35 Age [y:d:h:m:s]: 00:103:05:04:55
Block: 1118616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73793 RingCT/type: yes/0
Extra: 01bbc777b8553a14ab88e3df45c1fa0ef9b5cef34ef2f356e48315090a945ca60d021100000017e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2b8cbc20f1974b6f040d4bdc730f67b3e0466ecf827d11311f77ea885f757cf 0.600000000000 1599869 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": 1118626, "vin": [ { "gen": { "height": 1118616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2b8cbc20f1974b6f040d4bdc730f67b3e0466ecf827d11311f77ea885f757cf" } } ], "extra": [ 1, 187, 199, 119, 184, 85, 58, 20, 171, 136, 227, 223, 69, 193, 250, 14, 249, 181, 206, 243, 78, 242, 243, 86, 228, 131, 21, 9, 10, 148, 92, 166, 13, 2, 17, 0, 0, 0, 23, 233, 20, 221, 21, 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