Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 842c15c1140db5d289c48d3d076d62116793b4b417a4a37e0a936c28018178af

Tx prefix hash: f1bb46ac76ce5ce97cbb1eb87e120a2e198e93ce303f6ac39113426f9361ba6d
Tx public key: 287de011a9e404f4c0aa538817b7fd6a82c39be6f5c9a5979e1c886ae56746f2
Timestamp: 1723095233 Timestamp [UCT]: 2024-08-08 05:33:53 Age [y:d:h:m:s]: 00:115:17:18:13
Block: 1083215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82796 RingCT/type: yes/0
Extra: 01287de011a9e404f4c0aa538817b7fd6a82c39be6f5c9a5979e1c886ae56746f2021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a90ca2d3744d3f158b0c76a05bfdbd3030be1fa6bb2eb9ab71c6956cc52d3a6e 0.600000000000 1557054 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": 1083225, "vin": [ { "gen": { "height": 1083215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a90ca2d3744d3f158b0c76a05bfdbd3030be1fa6bb2eb9ab71c6956cc52d3a6e" } } ], "extra": [ 1, 40, 125, 224, 17, 169, 228, 4, 244, 192, 170, 83, 136, 23, 183, 253, 106, 130, 195, 155, 230, 245, 201, 165, 151, 158, 28, 136, 106, 229, 103, 70, 242, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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