Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc5b6698511c49b88535497590a565ba23514df072a70d469d12b90355701a98

Tx prefix hash: 2146e96a2506790fe1f8ad5ff44c16db5338bec588fad13f65fca60530c2d394
Tx public key: b1d1c69ae4dc13cba404ed67bcb1801d1a33d23f023fd926b29f6d5d01e5ea0c
Timestamp: 1726470135 Timestamp [UCT]: 2024-09-16 07:02:15 Age [y:d:h:m:s]: 00:128:12:15:07
Block: 1111187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91863 RingCT/type: yes/0
Extra: 01b1d1c69ae4dc13cba404ed67bcb1801d1a33d23f023fd926b29f6d5d01e5ea0c02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab066bb9fdec98701e08fbb7768755ec798196650434de8df0200f4fcd4478a9 0.600000000000 1590062 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": 1111197, "vin": [ { "gen": { "height": 1111187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab066bb9fdec98701e08fbb7768755ec798196650434de8df0200f4fcd4478a9" } } ], "extra": [ 1, 177, 209, 198, 154, 228, 220, 19, 203, 164, 4, 237, 103, 188, 177, 128, 29, 26, 51, 210, 63, 2, 63, 217, 38, 178, 159, 109, 93, 1, 229, 234, 12, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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