← previous blocknext block →recent activity
Analyzing
Block #105,843,574
20 transactions · 18 stateful · 2026-09-18 08:28:41 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,843,574 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w110w011w114w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81ca8c9e…28cb
0x34b655…2a6f
10 touches
10 conflicts
0xdfaa9666…2003
0x34b655…2a6f
10 touches
10 conflicts
0x6d955786…1327
0x34b655…2a6f
8 touches
6 conflicts
0x9210e826…1414
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x6d787177…e955
0x34b655…2a6f
4 touches
1 conflict
0x46b187cb…1733
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
10 conflicts on slot 0x81ca8c9e47…f128cb
Audit this contract →
← previous block·next block →recent activity