← previous blocknext block →recent activity
Analyzing
Block #107,848,935
16 transactions · 15 stateful · 2026-09-25 08:46:31 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,848,935 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w18w29w310w211w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b76a1fb…fdfc
0x34b655…2a6f
8 touches
6 conflicts
0xba522812…1f1f
0x34b655…2a6f
6 touches
3 conflicts
0x9901e91f…179b
0x34b655…2a6f
6 touches
3 conflicts
0x588380ee…0a5c
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xdc7b9eda…e616
0x34b655…2a6f
4 touches
1 conflict
0x03744646…5319
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 0x2b76a1fb53…5afdfc
Audit this contract →
← previous block·next block →recent activity