← previous blocknext block →recent activity
Analyzing
Block #107,817,346
16 transactions · 16 stateful · 2026-09-25 06:07:31 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,817,346 · 16 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
1w02w13w04w28w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdd97c21…e3d0
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c6
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xe9f2d21b…a28d
0xd32edf…ff58
5 touches
3 conflicts
0x0e3bc5b4…0a0b
0x34b655…2a6f
4 touches
1 conflict
0x3da20ed0…943a
0x34b655…2a6f
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
10 conflicts on slot 0xbdd97c213f…cee3d0
Audit this contract →
← previous block·next block →recent activity