← previous blocknext block →recent activity
Analyzing
Block #107,443,521
11 transactions · 11 stateful · 2026-09-23 22:43:54 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,443,521 · 11 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
2w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1b0
0x37db7f…ec7b
4 touches
1 conflict
0x3e4486b9…fa99
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x56f91464…1e91
0x37db7f…ec7b
3 touches
1 conflict
0x320e9d98…2abc
0x34b655…2a6f
2 touches
0 conflicts
0x33303721…96ed
0x34b655…2a6f
2 touches
0 conflicts
0x4856b443…1824
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity