Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa8bbc7594368b595ea61bcf846ed58d141e1d078fce80ae27967ce892832631

Tx prefix hash: eb34ec86d063f4dfc82b7a8af935370c0401a9c848fd18fca8442fd6a02466b8
Tx public key: 252c6a801fa316a7234be9e6616e6905c743f8c3394519b2cf4d4aec1cd90b9f
Timestamp: 1626361562 Timestamp [UCT]: 2021-07-15 15:06:02 Age [y:d:h:m:s]: 03:307:02:37:59
Block: 294574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 990467 RingCT/type: yes/0
Extra: 01252c6a801fa316a7234be9e6616e6905c743f8c3394519b2cf4d4aec1cd90b9f02110000000da6fe74fc000000000000000000

1 output(s) for total of 64.857776031000 dcy

stealth address amount amount idx
00: 6614ae68d4cebee705c82bdb57ea22dedd66b18c85831d4fbbb660e1dbef9a7d 64.857776031000 617046 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": 294584, "vin": [ { "gen": { "height": 294574 } } ], "vout": [ { "amount": 64857776031, "target": { "key": "6614ae68d4cebee705c82bdb57ea22dedd66b18c85831d4fbbb660e1dbef9a7d" } } ], "extra": [ 1, 37, 44, 106, 128, 31, 163, 22, 167, 35, 75, 233, 230, 97, 110, 105, 5, 199, 67, 248, 195, 57, 69, 25, 178, 207, 77, 74, 236, 28, 217, 11, 159, 2, 17, 0, 0, 0, 13, 166, 254, 116, 252, 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