Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22c1e71ed5469b67a3851fa555b0c1d3f88af1466746f8a621104f150756f66a

Tx prefix hash: d40ee903f91a1bdbf9676fc3355adf38674e708d7608fca7b385f8f613d37a3d
Tx public key: 2b165a02d3b423f297ad6eca083df50a2ffe87681e0529d18a4fd3be44a78a12
Timestamp: 1715353276 Timestamp [UCT]: 2024-05-10 15:01:16 Age [y:d:h:m:s]: 01:038:03:22:09
Block: 1019033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288081 RingCT/type: yes/0
Extra: 012b165a02d3b423f297ad6eca083df50a2ffe87681e0529d18a4fd3be44a78a1202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 264cb84163f5f3d576f263430aa40fc9a40229270b1bd84f158c7dbf83fae92b 0.600000000000 1482894 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": 1019043, "vin": [ { "gen": { "height": 1019033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "264cb84163f5f3d576f263430aa40fc9a40229270b1bd84f158c7dbf83fae92b" } } ], "extra": [ 1, 43, 22, 90, 2, 211, 180, 35, 242, 151, 173, 110, 202, 8, 61, 245, 10, 47, 254, 135, 104, 30, 5, 41, 209, 138, 79, 211, 190, 68, 167, 138, 18, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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