Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af6645d133f8d2992ccaa15519dc79d982e19f799e434cb016a055c61a4932c6

Tx prefix hash: fcd9a0f6ad5bdd7f3f6c546ca13eff7d8b0d0ebe0e795ffd184f8cda9749a6f2
Tx public key: c81b8ef152924e159ea5ed787ec1aae27c2f56a54f751bc8960e172f1c894a20
Timestamp: 1726500593 Timestamp [UCT]: 2024-09-16 15:29:53 Age [y:d:h:m:s]: 00:068:22:31:53
Block: 1111452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49283 RingCT/type: yes/0
Extra: 01c81b8ef152924e159ea5ed787ec1aae27c2f56a54f751bc8960e172f1c894a20021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70e13c2c699ea27b18f9d905e3f303ef0a9f13a3b437d4a6149cad7c021df411 0.600000000000 1590413 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": 1111462, "vin": [ { "gen": { "height": 1111452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70e13c2c699ea27b18f9d905e3f303ef0a9f13a3b437d4a6149cad7c021df411" } } ], "extra": [ 1, 200, 27, 142, 241, 82, 146, 78, 21, 158, 165, 237, 120, 126, 193, 170, 226, 124, 47, 86, 165, 79, 117, 27, 200, 150, 14, 23, 47, 28, 137, 74, 32, 2, 17, 0, 0, 0, 2, 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