Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e2ac5001def4931175bbf1fd56a13a4325fa0058bd93e3170a8c9eca867e079

Tx prefix hash: 94eb9996e7748febac19e19d9c66ec35c0cf6262593d0cc3d0265dfb8cee5e05
Tx public key: 1b894753ab52560530a210979f5a7ab5e9ba2d17ded682b2e268a74bb0f4015d
Timestamp: 1732056832 Timestamp [UCT]: 2024-11-19 22:53:52 Age [y:d:h:m:s]: 00:147:21:44:24
Block: 1157428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105523 RingCT/type: yes/0
Extra: 011b894753ab52560530a210979f5a7ab5e9ba2d17ded682b2e268a74bb0f4015d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5623bb7af63616bcb0e658731c5ab8f9e572e942c5e3baf75c8cc2ee9e4141e7 0.600000000000 1643051 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": 1157438, "vin": [ { "gen": { "height": 1157428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5623bb7af63616bcb0e658731c5ab8f9e572e942c5e3baf75c8cc2ee9e4141e7" } } ], "extra": [ 1, 27, 137, 71, 83, 171, 82, 86, 5, 48, 162, 16, 151, 159, 90, 122, 181, 233, 186, 45, 23, 222, 214, 130, 178, 226, 104, 167, 75, 176, 244, 1, 93, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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