← previous blocknext block →recent activity
Analyzing
Block #107,823,221
43 transactions · 38 stateful · 2026-09-25 06:37:06 UTC
Parallelism
70/100
Blocked
61%
Avg conflicts / tx
1.49
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #107,823,221 · 43 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w16w18w29w011w012w315w216w117w318w419w520w621w722w823w924w1026w1127w1228w129w231w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcd07321…1c31
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x3aed9088…e43c
0x34b655…2a6f
10 touches
10 conflicts
0xa7ba83b5…d0a8
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xba9f9225…2ead
0x34b655…2a6f
8 touches
6 conflicts
0xdd70c3e1…061b
0x34b655…2a6f
8 touches
6 conflicts
0x3a663e9a…a9c7
0x508254…98bd
6 touches
3 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
15 conflicts on slot 0xdcd0732149…7d1c31
Audit this contract →
← previous block·next block →recent activity