Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 354ae675092eb08ad2caa465573e26720e12bba3c11f9579fed78295dffed3d2

Tx prefix hash: 6665fefaf7d99d76d6c062aa8fb61ab2f05508c99216ce42811c1041837c04d1
Tx public key: e126ed1a3e12beb3f4215957411100c3bfe5fad96bdb9d1b97e9dd9bcd41b31e
Timestamp: 1724472475 Timestamp [UCT]: 2024-08-24 04:07:55 Age [y:d:h:m:s]: 00:265:08:14:12
Block: 1094646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189517 RingCT/type: yes/0
Extra: 01e126ed1a3e12beb3f4215957411100c3bfe5fad96bdb9d1b97e9dd9bcd41b31e021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7d088e6e86b4a32006ad580a957ca527f24e233b91d1c9c92a3606ef2122386 0.600000000000 1569765 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": 1094656, "vin": [ { "gen": { "height": 1094646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7d088e6e86b4a32006ad580a957ca527f24e233b91d1c9c92a3606ef2122386" } } ], "extra": [ 1, 225, 38, 237, 26, 62, 18, 190, 179, 244, 33, 89, 87, 65, 17, 0, 195, 191, 229, 250, 217, 107, 219, 157, 27, 151, 233, 221, 155, 205, 65, 179, 30, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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