Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e24d995f24bbcefe14c551ef834be5e047c6c8a00701e96676f9c7074a6a062b

Tx prefix hash: 20a52dc542da7ca70e337eafd239effde00f5ac6230c7a16f502788dfe2d0e4c
Tx public key: 65a0b61816911bd7f0775e3f2019c34bc4836a5ca742d96a6b27580dab3581ed
Timestamp: 1630009193 Timestamp [UCT]: 2021-08-26 20:19:53 Age [y:d:h:m:s]: 03:260:09:56:11
Block: 321372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 960461 RingCT/type: yes/0
Extra: 0165a0b61816911bd7f0775e3f2019c34bc4836a5ca742d96a6b27580dab3581ed021100000023baa4486c000000000000000000

1 output(s) for total of 52.864194030000 dcy

stealth address amount amount idx
00: 16c19a29a72fe1b7a2e38ca911f040ff11701e49d8f7e95df72d5e743035ee3a 52.864194030000 667174 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": 321382, "vin": [ { "gen": { "height": 321372 } } ], "vout": [ { "amount": 52864194030, "target": { "key": "16c19a29a72fe1b7a2e38ca911f040ff11701e49d8f7e95df72d5e743035ee3a" } } ], "extra": [ 1, 101, 160, 182, 24, 22, 145, 27, 215, 240, 119, 94, 63, 32, 25, 195, 75, 196, 131, 106, 92, 167, 66, 217, 106, 107, 39, 88, 13, 171, 53, 129, 237, 2, 17, 0, 0, 0, 35, 186, 164, 72, 108, 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