Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 538ac9e2cbe9792ba30a984e48f3c34710df82a4b95eef17c851dafa2ede4c61

Tx prefix hash: a22b585aa317cc59e0fc36894538d575e5c2d2863cfef965be346ae98425498e
Tx public key: 3fe3d0648d4b20914c14b2007305369a991195558a370d50364b0abea5f45df5
Timestamp: 1733228020 Timestamp [UCT]: 2024-12-03 12:13:40 Age [y:d:h:m:s]: 00:118:07:24:10
Block: 1167123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84354 RingCT/type: yes/0
Extra: 013fe3d0648d4b20914c14b2007305369a991195558a370d50364b0abea5f45df5021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fba48d182efea0a4eb0d8ade14a591c4c85ea84a47eb757c5742bf9203dbc425 0.600000000000 1652816 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": 1167133, "vin": [ { "gen": { "height": 1167123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fba48d182efea0a4eb0d8ade14a591c4c85ea84a47eb757c5742bf9203dbc425" } } ], "extra": [ 1, 63, 227, 208, 100, 141, 75, 32, 145, 76, 20, 178, 0, 115, 5, 54, 154, 153, 17, 149, 85, 138, 55, 13, 80, 54, 75, 10, 190, 165, 244, 93, 245, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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