← previous blocknext block →recent activity
Analyzing
Block #107,812,769
21 transactions · 19 stateful · 2026-09-25 05:44:29 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,812,769 · 21 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
2w03w14w09w010w111w212w314w415w516w118w119w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48203298…65cb
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x740fff9f…4244
0x34b655…2a6f
6 touches
3 conflicts
0xe98ab6b4…80ee
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x34a6145f…b17d
0x34b655…2a6f
4 touches
1 conflict
0x3da0a1e1…6d70
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 0x4820329863…2a65cb
Audit this contract →
← previous block·next block →recent activity