← previous blocknext block →recent activity
Analyzing
Block #107,442,289
13 transactions · 12 stateful · 2026-09-23 22:37:42 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,442,289 · 13 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
2w05w16w27w38w09w110w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
8 touches
6 conflicts
0xb066c72c…87d2
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x6286219a…0721
0x37db7f…ec7b
3 touches
1 conflict
0x56f91464…1e91
0x37db7f…ec7b
3 touches
1 conflict
0x5ba51e87…44ee
0x37db7f…ec7b
3 touches
1 conflict
0xa3d78e5e…bb33
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity