← previous blocknext block →recent activity
Analyzing
Block #107,849,032
19 transactions · 18 stateful · 2026-09-25 08:47:00 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,849,032 · 19 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
4w06w17w211w012w113w214w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb358e96b…6fc4
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x3aff72dc…a704
0x34b655…2a6f
4 touches
1 conflict
0x48972740…ad45
0x34b655…2a6f
4 touches
1 conflict
0x5e26f4ec…9b6c
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 0xb358e96b8f…8a6fc4
Audit this contract →
← previous block·next block →recent activity