← previous blocknext block →recent activity
Analyzing
Block #107,788,315
14 transactions · 13 stateful · 2026-09-25 03:41:18 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,788,315 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w09w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f3d1bb8…76b3
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x18cf84a6…09e4
0x34b655…2a6f
2 touches
0 conflicts
0x1cc2faa1…ee0a
0x34b655…2a6f
2 touches
0 conflicts
0x2249932e…474a
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x4f3d1bb8f9…a176b3
Audit this contract →
← previous block·next block →recent activity