Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 417fef4d41278bf5e32d8650af843586284a273fb503daf7baf4611e3ae22373

Tx prefix hash: 5b03e16067ea2d812225988e5410174aa313b4e04b1c0881ba37dfde36907ec2
Tx public key: 3734fe118cbd09be1ca61909eaae798bf0d10328a67822c1a1b5f9d2ebf07657
Timestamp: 1723396644 Timestamp [UCT]: 2024-08-11 17:17:24 Age [y:d:h:m:s]: 00:308:12:39:50
Block: 1085716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220335 RingCT/type: yes/0
Extra: 013734fe118cbd09be1ca61909eaae798bf0d10328a67822c1a1b5f9d2ebf07657021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5abae694e146008bf864d24640509b6faf1bbca774938d2a8ae9baf9f3baa36 0.600000000000 1560305 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": 1085726, "vin": [ { "gen": { "height": 1085716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5abae694e146008bf864d24640509b6faf1bbca774938d2a8ae9baf9f3baa36" } } ], "extra": [ 1, 55, 52, 254, 17, 140, 189, 9, 190, 28, 166, 25, 9, 234, 174, 121, 139, 240, 209, 3, 40, 166, 120, 34, 193, 161, 181, 249, 210, 235, 240, 118, 87, 2, 17, 0, 0, 0, 1, 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