Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a80a973508a124faa9b716898410964d9957a8005f4df602def8bc26f4ac366

Tx prefix hash: 69c3306a542ee80504b27fa327967582861526e8080e2bcb9d169d52e02d4081
Tx public key: 3189596d8823f8c8917d13db0b4f5e7d47ea6d753f8320e677fbf4177b41272a
Timestamp: 1675293909 Timestamp [UCT]: 2023-02-01 23:25:09 Age [y:d:h:m:s]: 01:287:13:58:15
Block: 687795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466472 RingCT/type: yes/0
Extra: 013189596d8823f8c8917d13db0b4f5e7d47ea6d753f8320e677fbf4177b41272a021100000001faf35c9c000000000000000000

1 output(s) for total of 3.228862706000 dcy

stealth address amount amount idx
00: 66fbf5760b30a9f45443d3792edd2aa1f4ca1364be3b59b91a78f6cf4cabe28f 3.228862706000 1130382 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": 687805, "vin": [ { "gen": { "height": 687795 } } ], "vout": [ { "amount": 3228862706, "target": { "key": "66fbf5760b30a9f45443d3792edd2aa1f4ca1364be3b59b91a78f6cf4cabe28f" } } ], "extra": [ 1, 49, 137, 89, 109, 136, 35, 248, 200, 145, 125, 19, 219, 11, 79, 94, 125, 71, 234, 109, 117, 63, 131, 32, 230, 119, 251, 244, 23, 123, 65, 39, 42, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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