Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16745f9771dac3985fb73e15ca0908dd4b633addb511066f9d4660032ce930f6

Tx prefix hash: 9229fed9d3cb23ae908a5bc6bc8fca0d4af3a74f2be989ed1ecc769f5c77fa79
Tx public key: def0dcf48786a9b4812b02bdec17f0cf5ada68f61f833d0da849805d9c0cb242
Timestamp: 1639742874 Timestamp [UCT]: 2021-12-17 12:07:54 Age [y:d:h:m:s]: 03:012:07:43:49
Block: 397467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 787755 RingCT/type: yes/0
Extra: 01def0dcf48786a9b4812b02bdec17f0cf5ada68f61f833d0da849805d9c0cb24202110000000137cb3088000000000000000000

1 output(s) for total of 29.581976501000 dcy

stealth address amount amount idx
00: 6c5913e043bf4914c2a71d792486ead9b6d7f8ea14aefe03701fff4735a75268 29.581976501000 796072 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": 397477, "vin": [ { "gen": { "height": 397467 } } ], "vout": [ { "amount": 29581976501, "target": { "key": "6c5913e043bf4914c2a71d792486ead9b6d7f8ea14aefe03701fff4735a75268" } } ], "extra": [ 1, 222, 240, 220, 244, 135, 134, 169, 180, 129, 43, 2, 189, 236, 23, 240, 207, 90, 218, 104, 246, 31, 131, 61, 13, 168, 73, 128, 93, 156, 12, 178, 66, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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