Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dda5c16904158ae4a0c439f5e0f8fc34ea73ac4c443536b11ac9088cb6479612

Tx prefix hash: f777930093fde6fd810f473675619e98ca36d46f76f7f1d83aa139e72884d2ef
Tx public key: a5512dc12d4ed5002e13e4ef4a9a4a8a1a61919092314b3536d6f3e81637e348
Timestamp: 1704086160 Timestamp [UCT]: 2024-01-01 05:16:00 Age [y:d:h:m:s]: 01:104:18:53:05
Block: 925616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336004 RingCT/type: yes/0
Extra: 01a5512dc12d4ed5002e13e4ef4a9a4a8a1a61919092314b3536d6f3e81637e3480211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a64f0d89dfeb2c57776d345719cd55240197264ea333300e3a49c71ad87d9d73 0.600000000000 1383380 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": 925626, "vin": [ { "gen": { "height": 925616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a64f0d89dfeb2c57776d345719cd55240197264ea333300e3a49c71ad87d9d73" } } ], "extra": [ 1, 165, 81, 45, 193, 45, 78, 213, 0, 46, 19, 228, 239, 74, 154, 74, 138, 26, 97, 145, 144, 146, 49, 75, 53, 54, 214, 243, 232, 22, 55, 227, 72, 2, 17, 0, 0, 0, 3, 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