Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abe39ea3a16109f4d84411882ea915dc4169ac9f425b5a6ff84aeeb264259c4c

Tx prefix hash: d29b4d4d1875e029f8af8272e98fb1471f47422bd835fbbd9c5822537e735d0a
Tx public key: f5185dfd2a0f93df91ffe3e855eee9fec7beab4ff40addd4c81e809bf17220ed
Timestamp: 1719048481 Timestamp [UCT]: 2024-06-22 09:28:01 Age [y:d:h:m:s]: 00:292:16:24:35
Block: 1049654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209161 RingCT/type: yes/0
Extra: 01f5185dfd2a0f93df91ffe3e855eee9fec7beab4ff40addd4c81e809bf17220ed02110000000791fab441000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb4a5b1009d40a7f68b378606cf0682d7b50389ee9ad8d26949aa8d2e0322599 0.600000000000 1519757 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": 1049664, "vin": [ { "gen": { "height": 1049654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb4a5b1009d40a7f68b378606cf0682d7b50389ee9ad8d26949aa8d2e0322599" } } ], "extra": [ 1, 245, 24, 93, 253, 42, 15, 147, 223, 145, 255, 227, 232, 85, 238, 233, 254, 199, 190, 171, 79, 244, 10, 221, 212, 200, 30, 128, 155, 241, 114, 32, 237, 2, 17, 0, 0, 0, 7, 145, 250, 180, 65, 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