Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8609eeaa5b7ade1c8c61bce1cad75202994adf45ba1e3071e5f4b905022def45

Tx prefix hash: fa44579212153f45c64ba72fec6b8725c8450285c143b34ada1d1860fd1fdc12
Tx public key: a7d92261c8e8323ba5a2c44d87f2ddf5ac2916223a05ad3a175e194eb7092162
Timestamp: 1712420918 Timestamp [UCT]: 2024-04-06 16:28:38 Age [y:d:h:m:s]: 00:363:08:55:35
Block: 994691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259813 RingCT/type: yes/0
Extra: 01a7d92261c8e8323ba5a2c44d87f2ddf5ac2916223a05ad3a175e194eb709216202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2c632f414ff968cfb065ab653643d82e08fc1bb9cb7b24b4bf1d5b95ebba11d 0.600000000000 1455095 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": 994701, "vin": [ { "gen": { "height": 994691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2c632f414ff968cfb065ab653643d82e08fc1bb9cb7b24b4bf1d5b95ebba11d" } } ], "extra": [ 1, 167, 217, 34, 97, 200, 232, 50, 59, 165, 162, 196, 77, 135, 242, 221, 245, 172, 41, 22, 34, 58, 5, 173, 58, 23, 94, 25, 78, 183, 9, 33, 98, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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