Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b426c5534d4004488e55b5d96c3fb95fbe80c66f783670b40343bb132b805081

Tx prefix hash: 922fb9cd37d379a5186bceda48a397e61dc9456b239523f9230e1a3f9f6b19e0
Tx public key: f62df70b382d2787d4d3ef628257fcec65e17c236ee5f1d632f35b56cfbf09c7
Timestamp: 1710047520 Timestamp [UCT]: 2024-03-10 05:12:00 Age [y:d:h:m:s]: 01:030:09:20:50
Block: 975053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282710 RingCT/type: yes/0
Extra: 01f62df70b382d2787d4d3ef628257fcec65e17c236ee5f1d632f35b56cfbf09c70211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bff1119330d0445f52132195114821faeb9685824f98126d9d6f4c1d14f96fb4 0.600000000000 1435024 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": 975063, "vin": [ { "gen": { "height": 975053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bff1119330d0445f52132195114821faeb9685824f98126d9d6f4c1d14f96fb4" } } ], "extra": [ 1, 246, 45, 247, 11, 56, 45, 39, 135, 212, 211, 239, 98, 130, 87, 252, 236, 101, 225, 124, 35, 110, 229, 241, 214, 50, 243, 91, 86, 207, 191, 9, 199, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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