← previous blocknext block →recent activity
Analyzing
Block #107,823,377
17 transactions · 16 stateful · 2026-09-25 06:37:53 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,823,377 · 17 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
4w05w17w18w09w110w211w312w415w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
6 touches
3 conflicts
0x25144f94…1854
0x34b655…2a6f
6 touches
3 conflicts
0xf865ea42…25bb
0x34b655…2a6f
6 touches
3 conflicts
0xa41c1a4f…f395
0xd32edf…ff58
5 touches
3 conflicts
0x42522e76…2592
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity