Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18b8dc15dcbdcb1826fff5914176decf4b2badec98cd7f32c76ad5d711bf1e49

Tx prefix hash: ef918c8ef8e0c8aded4e21e19b0cd4800e1107bab688212f11a22924cc657980
Tx public key: 333bb8ed3a059d2da424e1e0660362e9c2a2908633673e88f73ea5f4696c2ddd
Timestamp: 1706584004 Timestamp [UCT]: 2024-01-30 03:06:44 Age [y:d:h:m:s]: 01:275:19:25:22
Block: 946301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455925 RingCT/type: yes/0
Extra: 01333bb8ed3a059d2da424e1e0660362e9c2a2908633673e88f73ea5f4696c2ddd0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89dedef6c1e61d02a189fd27859f83becaf1c55f4ffaebf895388a64a82af632 0.600000000000 1404633 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": 946311, "vin": [ { "gen": { "height": 946301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89dedef6c1e61d02a189fd27859f83becaf1c55f4ffaebf895388a64a82af632" } } ], "extra": [ 1, 51, 59, 184, 237, 58, 5, 157, 45, 164, 36, 225, 224, 102, 3, 98, 233, 194, 162, 144, 134, 51, 103, 62, 136, 247, 62, 165, 244, 105, 108, 45, 221, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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