Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fada2342af41a86c82fe5338eff67458e4d7e31d323ca495046a44ed894e214b

Tx prefix hash: cd328ff59b3ceec39776e8f198fbd3fe83de3a122d294fbf9d13a198992d4096
Tx public key: 879e287a37249c87cf46b92f3fc7e911e04a597edf6f9b7e81f08299e5042df8
Timestamp: 1699640716 Timestamp [UCT]: 2023-11-10 18:25:16 Age [y:d:h:m:s]: 01:140:01:36:53
Block: 888767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361294 RingCT/type: yes/0
Extra: 01879e287a37249c87cf46b92f3fc7e911e04a597edf6f9b7e81f08299e5042df802110000000533af99f4000000000000000000

1 output(s) for total of 0.696860718000 dcy

stealth address amount amount idx
00: 29005e2b6a5cbfa7db752faecf305037ed5ec93ae0c3f1e6a3789201edc9c9d7 0.696860718000 1344726 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": 888777, "vin": [ { "gen": { "height": 888767 } } ], "vout": [ { "amount": 696860718, "target": { "key": "29005e2b6a5cbfa7db752faecf305037ed5ec93ae0c3f1e6a3789201edc9c9d7" } } ], "extra": [ 1, 135, 158, 40, 122, 55, 36, 156, 135, 207, 70, 185, 47, 63, 199, 233, 17, 224, 74, 89, 126, 223, 111, 155, 126, 129, 240, 130, 153, 229, 4, 45, 248, 2, 17, 0, 0, 0, 5, 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