← previous blocknext block →recent activity
Analyzing
Block #109,133,826
22 transactions · 19 stateful · 2026-09-29 20:40:35 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,133,826 · 22 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
1w010w011w112w213w314w415w516w620w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65ec5427…5e30
0x34b655…2a6f
14 touches
21 conflicts
0x1867b653…e61b
0x34b655…2a6f
8 touches
6 conflicts
0xefbc8547…fc92
0x34b655…2a6f
6 touches
3 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
6 touches
3 conflicts
0xbaf77397…e798
0x34b655…2a6f
6 touches
3 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0x06d6349e…686d
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
21 conflicts on slot 0x65ec5427ea…1b5e30
Audit this contract →
← previous block·next block →recent activity