Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5e60e9389fa591950a6d480cecd36cb9ee3b7dfb02fb724eac7b880c9a4259a

Tx prefix hash: 15056b92d2b8a70704a577ddad1374db856beb8717d740d6d0db6d4d5d59544a
Tx public key: ac97d45ad6e29e94e583db945a49f31e2120472a3cc3c86ceaf055cb69bf2a29
Timestamp: 1731490996 Timestamp [UCT]: 2024-11-13 09:43:16 Age [y:d:h:m:s]: 01:051:19:16:50
Block: 1152728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295517 RingCT/type: yes/0
Extra: 01ac97d45ad6e29e94e583db945a49f31e2120472a3cc3c86ceaf055cb69bf2a290211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6f4d60e79773de10839990a1673f139a97ead9829cc7cf4deed69b1a6ac5fcd 0.600000000000 1638331 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": 1152738, "vin": [ { "gen": { "height": 1152728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6f4d60e79773de10839990a1673f139a97ead9829cc7cf4deed69b1a6ac5fcd" } } ], "extra": [ 1, 172, 151, 212, 90, 214, 226, 158, 148, 229, 131, 219, 148, 90, 73, 243, 30, 33, 32, 71, 42, 60, 195, 200, 108, 234, 240, 85, 203, 105, 191, 42, 41, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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