← previous blocknext block →recent activity
Analyzing
Block #109,176,933
22 transactions · 17 stateful · 2026-09-30 00:17:54 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,176,933 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w08w09w110w115w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16d77246…bac5
0x34b655…2a6f
4 touches
1 conflict
0x21bce2a9…2469
0x34b655…2a6f
4 touches
1 conflict
0x280aaa58…1c52
0x34b655…2a6f
4 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
4 touches
1 conflict
0x487cc6ea…24a5
0x34b655…2a6f
4 touches
1 conflict
0x5969523e…5191
0x34b655…2a6f
4 touches
1 conflict
0x5b4c80c8…c242
0x34b655…2a6f
4 touches
1 conflict
0x7d9ef283…ddd1
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
1 conflict on slot 0x16d7724673…ecbac5
Audit this contract →
← previous block·next block →recent activity