Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1ce3d4ff720a118cf4412f6ab120f7a04d7e76dcdcb74da8571c2881c2420b7

Tx prefix hash: 460d2f4af6a38a259974544657c5b4e15f452da348c7403d9599c9f8d36ab08a
Tx public key: ba50e9333f49ac153525d04c594416d155550fbdaaf345126a37d957fc3c73a9
Timestamp: 1699726385 Timestamp [UCT]: 2023-11-11 18:13:05 Age [y:d:h:m:s]: 01:170:18:29:00
Block: 889476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383253 RingCT/type: yes/0
Extra: 01ba50e9333f49ac153525d04c594416d155550fbdaaf345126a37d957fc3c73a9021100000005faf35c9c000000000000000000

1 output(s) for total of 0.693101393000 dcy

stealth address amount amount idx
00: e11bdb7098d8bf938225b9b1b529b9bd7fbd83099be39a662f65de101a7f0f46 0.693101393000 1345475 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": 889486, "vin": [ { "gen": { "height": 889476 } } ], "vout": [ { "amount": 693101393, "target": { "key": "e11bdb7098d8bf938225b9b1b529b9bd7fbd83099be39a662f65de101a7f0f46" } } ], "extra": [ 1, 186, 80, 233, 51, 63, 73, 172, 21, 53, 37, 208, 76, 89, 68, 22, 209, 85, 85, 15, 189, 170, 243, 69, 18, 106, 55, 217, 87, 252, 60, 115, 169, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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