Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57757b63cc1f8f0e33180996f09222827ac1fbfe6cc6a445cec60fdaf2b7a648

Tx prefix hash: 30d33aa5e8cba07e188bc4aa49ca75a63baed902898b2a6869f989747eae3281
Tx public key: c64073e6ebc9cb0320e51f40e20960d7e56b2c543ddcc38187b7e40c5062dbec
Timestamp: 1735111281 Timestamp [UCT]: 2024-12-25 07:21:21 Age [y:d:h:m:s]: 00:088:19:53:13
Block: 1182737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63236 RingCT/type: yes/0
Extra: 01c64073e6ebc9cb0320e51f40e20960d7e56b2c543ddcc38187b7e40c5062dbec021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 374a076e31ab5430560b6162a3902b1ecd942d4e2807b254f191ae7e66f385f2 0.600000000000 1669174 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": 1182747, "vin": [ { "gen": { "height": 1182737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "374a076e31ab5430560b6162a3902b1ecd942d4e2807b254f191ae7e66f385f2" } } ], "extra": [ 1, 198, 64, 115, 230, 235, 201, 203, 3, 32, 229, 31, 64, 226, 9, 96, 215, 229, 107, 44, 84, 61, 220, 195, 129, 135, 183, 228, 12, 80, 98, 219, 236, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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