Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 524896f7f4aefdd6ba5ddc05dab9576fa3d1d7b946e7567c54f2034c20cb7ea5

Tx prefix hash: 8bd6211a5e37cddcd54581ffed4b91077c1a3e09282cd2cd7f68b31c35b7a1b6
Tx public key: 02114c99e2670af839d79ae18e8245a9c84c87a9e0e4f2f638e93ceba3983cad
Timestamp: 1698501741 Timestamp [UCT]: 2023-10-28 14:02:21 Age [y:d:h:m:s]: 01:171:18:08:35
Block: 879541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383749 RingCT/type: yes/0
Extra: 0102114c99e2670af839d79ae18e8245a9c84c87a9e0e4f2f638e93ceba3983cad02110000000279bda3be000000000000000000

1 output(s) for total of 0.747679659000 dcy

stealth address amount amount idx
00: 14d2c6115e2aee9b444a088a918350d5c9b538aa824d74be74b29221e8d7ef19 0.747679659000 1335069 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": 879551, "vin": [ { "gen": { "height": 879541 } } ], "vout": [ { "amount": 747679659, "target": { "key": "14d2c6115e2aee9b444a088a918350d5c9b538aa824d74be74b29221e8d7ef19" } } ], "extra": [ 1, 2, 17, 76, 153, 226, 103, 10, 248, 57, 215, 154, 225, 142, 130, 69, 169, 200, 76, 135, 169, 224, 228, 242, 246, 56, 233, 60, 235, 163, 152, 60, 173, 2, 17, 0, 0, 0, 2, 121, 189, 163, 190, 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