Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94cb5e21e6b78a0704ebaa4246fa1501b2b2861fb1e0f42863b4f43bdf18527b

Tx prefix hash: f75a11573c9e388f02c4ab4d605b2708281a94eee24910330e5461a343fdd27e
Tx public key: ce10597284db503b702df5e9c76fa604d2a59ebcb43610366a4a03262dd888d6
Timestamp: 1711889822 Timestamp [UCT]: 2024-03-31 12:57:02 Age [y:d:h:m:s]: 01:017:17:02:44
Block: 990340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273608 RingCT/type: yes/0
Extra: 01ce10597284db503b702df5e9c76fa604d2a59ebcb43610366a4a03262dd888d602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 385e6e0c5bb21ce1aee3c0b0d66b9d5caab36321f5e553de3c5f85995bb29b15 0.600000000000 1450662 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": 990350, "vin": [ { "gen": { "height": 990340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "385e6e0c5bb21ce1aee3c0b0d66b9d5caab36321f5e553de3c5f85995bb29b15" } } ], "extra": [ 1, 206, 16, 89, 114, 132, 219, 80, 59, 112, 45, 245, 233, 199, 111, 166, 4, 210, 165, 158, 188, 180, 54, 16, 54, 106, 74, 3, 38, 45, 216, 136, 214, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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