Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d667af010b22a947e1a540ada6dc45a61a9e912f00809b0c596c563e96843c64

Tx prefix hash: 2ffc2d99e5ee2dce216fc575199158911d336d4df5b0fcda90292d1a8927d36d
Tx public key: 219dcc87463f2a9d160483791aad3ecf2da144c14b20c02b377cb9a0200ed045
Timestamp: 1709046764 Timestamp [UCT]: 2024-02-27 15:12:44 Age [y:d:h:m:s]: 01:039:02:17:21
Block: 966754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288937 RingCT/type: yes/0
Extra: 01219dcc87463f2a9d160483791aad3ecf2da144c14b20c02b377cb9a0200ed0450211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04fccd3882324540a15d307ffe26ab2d4d5150df22a1e874ee351ea1e1f0c1ce 0.600000000000 1426525 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": 966764, "vin": [ { "gen": { "height": 966754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04fccd3882324540a15d307ffe26ab2d4d5150df22a1e874ee351ea1e1f0c1ce" } } ], "extra": [ 1, 33, 157, 204, 135, 70, 63, 42, 157, 22, 4, 131, 121, 26, 173, 62, 207, 45, 161, 68, 193, 75, 32, 192, 43, 55, 124, 185, 160, 32, 14, 208, 69, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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