← previous blocknext block →recent activity
Analyzing
Block #106,242,164
22 transactions · 21 stateful · 2026-09-19 17:55:53 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,242,164 · 22 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
1w02w13w24w110w011w112w213w315w016w117w218w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01afdc8b…8101
0x6f6493…b480
8 touches
6 conflicts
0x0a2d2aa5…1dff
0x6f6493…b480
8 touches
6 conflicts
0x11d9695c…0597
0x6f6493…b480
8 touches
6 conflicts
0x1629a315…cb78
0x6f6493…b480
8 touches
6 conflicts
0x2916b004…f6e0
0x6f6493…b480
8 touches
6 conflicts
0x2abb0606…5a0d
0x6f6493…b480
8 touches
6 conflicts
0x42ac3e7f…b91b
0x6f6493…b480
8 touches
6 conflicts
0x44ee0e4a…271d
0x6f6493…b480
8 touches
6 conflicts
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: 0x6f6493e3…08b480
6 conflicts on slot 0x01afdc8bbd…0f8101
Audit this contract →
← previous block·next block →recent activity