Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9613f7711afc86726138bdfc1a6e6a2880d6e28aaf5424c2d91e8e0fbc92f21b

Tx prefix hash: 13d3e6e2d34b99d1d2a8558e916b158ef00b1daf3a1526231d31a91067b0dad9
Tx public key: afe3268400734c55c6254a29f45ad80421bda2d17a5e24cb292eff74fe2bbdc4
Timestamp: 1684994979 Timestamp [UCT]: 2023-05-25 06:09:39 Age [y:d:h:m:s]: 02:025:00:29:51
Block: 767597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 539875 RingCT/type: yes/0
Extra: 01afe3268400734c55c6254a29f45ad80421bda2d17a5e24cb292eff74fe2bbdc4021100000002b3164c24000000000000000000

1 output(s) for total of 1.756437383000 dcy

stealth address amount amount idx
00: 5028fc86a816cdd09d0a9617e1a6194147378d12de405b5035e0517e35741bbe 1.756437383000 1216728 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": 767607, "vin": [ { "gen": { "height": 767597 } } ], "vout": [ { "amount": 1756437383, "target": { "key": "5028fc86a816cdd09d0a9617e1a6194147378d12de405b5035e0517e35741bbe" } } ], "extra": [ 1, 175, 227, 38, 132, 0, 115, 76, 85, 198, 37, 74, 41, 244, 90, 216, 4, 33, 189, 162, 209, 122, 94, 36, 203, 41, 46, 255, 116, 254, 43, 189, 196, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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