Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e7c2917c23755ccd8ba5ea566390a5ef2f2131541a85d36e7570d9e526dacbd

Tx prefix hash: 3302654e1d11a59164d74cdd61b7326d548f54ce7351eb619599a6e65eddf7b0
Tx public key: 641acc2273e6a8e12a2d3292bb866c811ba56c7c38cd640330fa7c4be7aa89f0
Timestamp: 1726251308 Timestamp [UCT]: 2024-09-13 18:15:08 Age [y:d:h:m:s]: 01:062:05:22:32
Block: 1109381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302895 RingCT/type: yes/0
Extra: 01641acc2273e6a8e12a2d3292bb866c811ba56c7c38cd640330fa7c4be7aa89f0021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d06683372200f8d80f930f27a148ebc2f21c0800c5ffde5e5ae2059b6a6698cc 0.600000000000 1587610 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": 1109391, "vin": [ { "gen": { "height": 1109381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d06683372200f8d80f930f27a148ebc2f21c0800c5ffde5e5ae2059b6a6698cc" } } ], "extra": [ 1, 100, 26, 204, 34, 115, 230, 168, 225, 42, 45, 50, 146, 187, 134, 108, 129, 27, 165, 108, 124, 56, 205, 100, 3, 48, 250, 124, 75, 231, 170, 137, 240, 2, 17, 0, 0, 0, 3, 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