Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f78a74f78357b6b28adc1c01c7fab78abb64bb8212447b6c46ded0ed964b3b5

Tx prefix hash: 4e578999d9a1b6ca93a0bcb67b33129b5c4e330aa92363cb78089875c6053df9
Tx public key: db6a2bb3280e80862090f4d1869524a2b3cb9768341e166f7c48a7e1c84a8987
Timestamp: 1702205116 Timestamp [UCT]: 2023-12-10 10:45:16 Age [y:d:h:m:s]: 01:145:13:24:15
Block: 910030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365185 RingCT/type: yes/0
Extra: 01db6a2bb3280e80862090f4d1869524a2b3cb9768341e166f7c48a7e1c84a898702110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0af8bb37d1f3bb1c5e60d5d1a90151818db4439b5fa1f688721617a17d060092 0.600000000000 1367171 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": 910040, "vin": [ { "gen": { "height": 910030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0af8bb37d1f3bb1c5e60d5d1a90151818db4439b5fa1f688721617a17d060092" } } ], "extra": [ 1, 219, 106, 43, 179, 40, 14, 128, 134, 32, 144, 244, 209, 134, 149, 36, 162, 179, 203, 151, 104, 52, 30, 22, 111, 124, 72, 167, 225, 200, 74, 137, 135, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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