Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be8b2444203c83ec5ef301e09796d87e96fcc3f71900de3a1af8732d805a1a0e

Tx prefix hash: a10a6c485f1ac858fe94e28a4fc364cd58db281ea25831404a4b944290d37416
Tx public key: 79a93473df227f9ff8c4cdf801a491549afdf93da20891573f1ce1c5dfc7fa5a
Timestamp: 1700922677 Timestamp [UCT]: 2023-11-25 14:31:17 Age [y:d:h:m:s]: 01:143:15:23:39
Block: 899400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363832 RingCT/type: yes/0
Extra: 0179a93473df227f9ff8c4cdf801a491549afdf93da20891573f1ce1c5dfc7fa5a021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.642561093000 dcy

stealth address amount amount idx
00: 51c5f34caa97048dc77e8060ad4aea63c77a01b23d83cceb88fc19874373048e 0.642561093000 1355853 of 0

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": 899410, "vin": [ { "gen": { "height": 899400 } } ], "vout": [ { "amount": 642561093, "target": { "key": "51c5f34caa97048dc77e8060ad4aea63c77a01b23d83cceb88fc19874373048e" } } ], "extra": [ 1, 121, 169, 52, 115, 223, 34, 127, 159, 248, 196, 205, 248, 1, 164, 145, 84, 154, 253, 249, 61, 162, 8, 145, 87, 63, 28, 225, 197, 223, 199, 250, 90, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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