Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7760384819b912a4e6ca876b3dfb1036be6cb4ea0105a23ca5a1c00b3909dcb3

Tx prefix hash: fa0596c51a25023e892ed4d25ef09660c92e8f3a26639f5bf484b2187bb20a12
Tx public key: 86077a039d6e06ff1003956898f0cdab4df37c666708408b5bc6b25db663993a
Timestamp: 1729651822 Timestamp [UCT]: 2024-10-23 02:50:22 Age [y:d:h:m:s]: 00:032:12:49:14
Block: 1137545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23246 RingCT/type: yes/0
Extra: 0186077a039d6e06ff1003956898f0cdab4df37c666708408b5bc6b25db663993a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfc28df98fdf5b6d284d21a61d848b8293c394aee9d85b8344a0ef3d074f4960 0.600000000000 1621056 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": 1137555, "vin": [ { "gen": { "height": 1137545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfc28df98fdf5b6d284d21a61d848b8293c394aee9d85b8344a0ef3d074f4960" } } ], "extra": [ 1, 134, 7, 122, 3, 157, 110, 6, 255, 16, 3, 149, 104, 152, 240, 205, 171, 77, 243, 124, 102, 103, 8, 64, 139, 91, 198, 178, 93, 182, 99, 153, 58, 2, 17, 0, 0, 0, 2, 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