← previous blocknext block →recent activity
Analyzing
Block #107,839,646
13 transactions · 13 stateful · 2026-09-25 07:59:45 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,839,646 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xa7ba83b5…d0a8
0x34b655…2a6f
4 touches
1 conflict
0xc6aa4ea3…dccb
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xee757899…302b
0x34b655…2a6f
4 touches
1 conflict
0x25144f94…1854
0x34b655…2a6f
4 touches
1 conflict
0x3750b746…5a9e
0x34b655…2a6f
4 touches
1 conflict
0x3a7fb5b5…f0e5
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