Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3f68b5a1bb20a66ca0bd182af242a162c6286ae14140873b6ba763494fa9c48

Tx prefix hash: 1c8e790e3849c7f966d08239bd0d0477cae9c7e467f354163e204f32643100b8
Tx public key: 5d577443085ebca3dbc8c040aeaaf6bfbbdc83772c5873037e3d7f912471c2a6
Timestamp: 1720926555 Timestamp [UCT]: 2024-07-14 03:09:15 Age [y:d:h:m:s]: 01:117:09:28:36
Block: 1065252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342391 RingCT/type: yes/0
Extra: 015d577443085ebca3dbc8c040aeaaf6bfbbdc83772c5873037e3d7f912471c2a602110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27b6145dbdf637b0b6e98b6e9b012b784e9506386400a6bdf54394cebd1811ed 0.600000000000 1535797 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": 1065262, "vin": [ { "gen": { "height": 1065252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27b6145dbdf637b0b6e98b6e9b012b784e9506386400a6bdf54394cebd1811ed" } } ], "extra": [ 1, 93, 87, 116, 67, 8, 94, 188, 163, 219, 200, 192, 64, 174, 170, 246, 191, 187, 220, 131, 119, 44, 88, 115, 3, 126, 61, 127, 145, 36, 113, 194, 166, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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