← previous blocknext block →recent activity
Analyzing
Block #109,143,133
21 transactions · 16 stateful · 2026-09-29 21:27:25 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,143,133 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w18w210w312w414w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
10 touches
10 conflicts
0x5969523e…5191
0x34b655…2a6f
10 touches
10 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
10 touches
10 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
10 touches
10 conflicts
0xb7e8b0c4…dec3
0x34b655…2a6f
10 touches
10 conflicts
0xdc1ee9ba…027d
0x34b655…2a6f
10 touches
10 conflicts
0xeacb4513…9af9
0x34b655…2a6f
10 touches
10 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: Perpl
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity