← previous blocknext block →recent activity
Analyzing
Block #106,951,430
23 transactions · 22 stateful · 2026-09-22 05:26:36 UTC
Parallelism
65/100
Blocked
45%
Avg conflicts / tx
0.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,951,430 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w29w210w312w413w115w016w118w520w021w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37ad906a…ae75
0x34b655…2a6f
8 touches
6 conflicts
0x9edb502d…1cf9
0x34b655…2a6f
8 touches
6 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0x8f18c248…9da5
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
6 conflicts on slot 0x37ad906a14…7aae75
Audit this contract →
← previous block·next block →recent activity