Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa9044d195755c3daa5feda2938681d5fdae2b1bc1d23944c26f43c74bcd7689

Tx prefix hash: 35e1f32f5f428e0bb55618903a3affac25fa06dcd8c539179fd86f8ba1217b0d
Tx public key: 6a8d4e287b0e35e61e4271b701a317c1b2dc648680de315d97a1b9da1badda5c
Timestamp: 1737345714 Timestamp [UCT]: 2025-01-20 04:01:54 Age [y:d:h:m:s]: 00:149:19:49:19
Block: 1201167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106809 RingCT/type: yes/0
Extra: 016a8d4e287b0e35e61e4271b701a317c1b2dc648680de315d97a1b9da1badda5c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb808782adf35ce0c624df499ed31dbe200867a4f3e57b80dd888faa19198823 0.600000000000 1687816 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": 1201177, "vin": [ { "gen": { "height": 1201167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb808782adf35ce0c624df499ed31dbe200867a4f3e57b80dd888faa19198823" } } ], "extra": [ 1, 106, 141, 78, 40, 123, 14, 53, 230, 30, 66, 113, 183, 1, 163, 23, 193, 178, 220, 100, 134, 128, 222, 49, 93, 151, 161, 185, 218, 27, 173, 218, 92, 2, 17, 0, 0, 0, 4, 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