Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eee897149afb3549724031d386f4b63e0cf3cf9d9f72706f851336c4c3e65574

Tx prefix hash: 92c84dcb6a170fdbca983554d13734c9781dae3311d957380322b3aed3aaf4c1
Tx public key: 61cedeff2f5077b64f1e0fd5c6aba1cce2c412972c12be7108e4fa14f2b2ea5c
Timestamp: 1714670081 Timestamp [UCT]: 2024-05-02 17:14:41 Age [y:d:h:m:s]: 00:249:22:49:11
Block: 1013372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178900 RingCT/type: yes/0
Extra: 0161cedeff2f5077b64f1e0fd5c6aba1cce2c412972c12be7108e4fa14f2b2ea5c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb162304a37433441512d77a21cc9e01914c002d79d2a495b7e901c8bf28bdd2 0.600000000000 1476171 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": 1013382, "vin": [ { "gen": { "height": 1013372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb162304a37433441512d77a21cc9e01914c002d79d2a495b7e901c8bf28bdd2" } } ], "extra": [ 1, 97, 206, 222, 255, 47, 80, 119, 182, 79, 30, 15, 213, 198, 171, 161, 204, 226, 196, 18, 151, 44, 18, 190, 113, 8, 228, 250, 20, 242, 178, 234, 92, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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