Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76267f0e54d6008eebfd0dca2838daacc6cd7a0eb8ce56c57b49f452872c798f

Tx prefix hash: a1a03065fde37a47fd4762918778ca5db57406d617ffe7250c16025bc2ca925e
Tx public key: b139c7b273ca1efd556ff333e90a7b1a51ef38ef40ec93fb4b7d742e6e63efa8
Timestamp: 1701222193 Timestamp [UCT]: 2023-11-29 01:43:13 Age [y:d:h:m:s]: 01:053:15:04:25
Block: 901864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299675 RingCT/type: yes/0
Extra: 01b139c7b273ca1efd556ff333e90a7b1a51ef38ef40ec93fb4b7d742e6e63efa802110000000933af99f4000000000000000000

1 output(s) for total of 0.630594483000 dcy

stealth address amount amount idx
00: 0f0c33295067491804ff869eae1c136f63eb0139f2f355959db9fba93b516435 0.630594483000 1358457 of 0

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": 901874, "vin": [ { "gen": { "height": 901864 } } ], "vout": [ { "amount": 630594483, "target": { "key": "0f0c33295067491804ff869eae1c136f63eb0139f2f355959db9fba93b516435" } } ], "extra": [ 1, 177, 57, 199, 178, 115, 202, 30, 253, 85, 111, 243, 51, 233, 10, 123, 26, 81, 239, 56, 239, 64, 236, 147, 251, 75, 125, 116, 46, 110, 99, 239, 168, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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