Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e309e30e120f822514536c71db3ee46e4cf714a4489d60781e3885b22c1bdbca

Tx prefix hash: 0e1f3ca74056f1721f42bff090550503943506ebdc2d660a3babd655004fd9c5
Tx public key: a16dfc615c7458f1857a09cb49ca6ddc72b65f6b7d2165673ebd8169b2cb6df5
Timestamp: 1729947111 Timestamp [UCT]: 2024-10-26 12:51:51 Age [y:d:h:m:s]: 00:234:20:30:07
Block: 1139987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167577 RingCT/type: yes/0
Extra: 01a16dfc615c7458f1857a09cb49ca6ddc72b65f6b7d2165673ebd8169b2cb6df50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3174dd0bb7f84fc10c545b27ce55c827326a7a84c59540fe6260fad3260ee8cc 0.600000000000 1623776 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": 1139997, "vin": [ { "gen": { "height": 1139987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3174dd0bb7f84fc10c545b27ce55c827326a7a84c59540fe6260fad3260ee8cc" } } ], "extra": [ 1, 161, 109, 252, 97, 92, 116, 88, 241, 133, 122, 9, 203, 73, 202, 109, 220, 114, 182, 95, 107, 125, 33, 101, 103, 62, 189, 129, 105, 178, 203, 109, 245, 2, 17, 0, 0, 0, 1, 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