← previous blocknext block →recent activity
Analyzing
Block #109,237,819
25 transactions · 20 stateful · 2026-09-30 05:24:22 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,237,819 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w010w112w213w114w218w219w022w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8313d5c…8ef5
0x34b655…2a6f
6 touches
3 conflicts
0x3484c2c1…d9a4
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0x6a45b0bf…ecd7
0x34b655…2a6f
4 touches
1 conflict
0x731d7308…fd26
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
3 conflicts on slot 0xb8313d5c48…658ef5
Audit this contract →
← previous block·next block →recent activity