Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8c74ed848137ce3ed073c537bb0b872ad72dbb4ef000107322561bbf327d17d

Tx prefix hash: 8ee17e3b1ad8fca17aaa34e1a471e00a3b4be37712f8c49c79a8bc48e2323a0c
Tx public key: 6d64481c23f2674b5fe9b44e33eb23f4af2d38a39c913e4387070efd056921c3
Timestamp: 1717607993 Timestamp [UCT]: 2024-06-05 17:19:53 Age [y:d:h:m:s]: 00:290:16:24:39
Block: 1037729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207732 RingCT/type: yes/0
Extra: 016d64481c23f2674b5fe9b44e33eb23f4af2d38a39c913e4387070efd056921c302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36dea3cb7a840ec161c3f601f6c7f89c45670f5ddbc3d7b30949f2aaad1aca48 0.600000000000 1506284 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": 1037739, "vin": [ { "gen": { "height": 1037729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36dea3cb7a840ec161c3f601f6c7f89c45670f5ddbc3d7b30949f2aaad1aca48" } } ], "extra": [ 1, 109, 100, 72, 28, 35, 242, 103, 75, 95, 233, 180, 78, 51, 235, 35, 244, 175, 45, 56, 163, 156, 145, 62, 67, 135, 7, 14, 253, 5, 105, 33, 195, 2, 17, 0, 0, 0, 1, 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