← previous blocknext block →recent activity
Analyzing
Block #107,813,658
23 transactions · 19 stateful · 2026-09-25 05:48:58 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,813,658 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w19w010w111w212w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb21158b…f18d
0x34b655…2a6f
8 touches
6 conflicts
0x13061ff4…3331
0x34b655…2a6f
8 touches
6 conflicts
0x961c0cd9…0937
0x34b655…2a6f
8 touches
6 conflicts
0xba522812…1f1f
0x34b655…2a6f
8 touches
6 conflicts
0xd87f1ed1…59f0
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x42522e76…2592
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 0xcb21158b83…66f18d
Audit this contract →
← previous block·next block →recent activity