Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a77d684ece7e7bb3d8f341e777ceb51674e9f1741326df408353431fbf37365d

Tx prefix hash: d59933ad3f95cb8ee3a1a083118abe452b048f6d7018de356f5f1f20ecf9417f
Tx public key: 6bf26c0e7e128426f349c912c5bf479323ad2b3aa298c2f5b96db816baa336ec
Timestamp: 1712608720 Timestamp [UCT]: 2024-04-08 20:38:40 Age [y:d:h:m:s]: 01:037:15:50:23
Block: 996249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287916 RingCT/type: yes/0
Extra: 016bf26c0e7e128426f349c912c5bf479323ad2b3aa298c2f5b96db816baa336ec02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e38d504e5ec5d9a060ac32cc88bbca46f7212161d963683513aa4a393d30a803 0.600000000000 1456665 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": 996259, "vin": [ { "gen": { "height": 996249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e38d504e5ec5d9a060ac32cc88bbca46f7212161d963683513aa4a393d30a803" } } ], "extra": [ 1, 107, 242, 108, 14, 126, 18, 132, 38, 243, 73, 201, 18, 197, 191, 71, 147, 35, 173, 43, 58, 162, 152, 194, 245, 185, 109, 184, 22, 186, 163, 54, 236, 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