← previous blocknext block →recent activity
Analyzing
Block #107,847,807
20 transactions · 19 stateful · 2026-09-25 08:40:50 UTC
Parallelism
75/100
Blocked
26%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,847,807 · 20 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
5w07w08w09w110w211w312w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x047e4986…f8de
0x851145…3f07
4 touches
1 conflict
0x05e3d4c1…f5cc
0x851145…3f07
4 touches
1 conflict
0xaa396bc0…9f3f
0x851145…3f07
4 touches
1 conflict
0xecff7c35…1b43
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
3 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity