← previous blocknext block →recent activity
Analyzing
Block #107,278,338
18 transactions · 17 stateful · 2026-09-23 08:52:27 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,278,338 · 18 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
1w02w13w24w35w410w511w312w416w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
6 touches
3 conflicts
0x9f46242e…f550
0x34b655…2a6f
6 touches
3 conflicts
0x96169450…af67
0xd32edf…ff58
5 touches
3 conflicts
0x050d7a8a…67d0
0x34b655…2a6f
4 touches
1 conflict
0x1d02654c…ff86
0x34b655…2a6f
4 touches
1 conflict
0x1ee57dc9…5a51
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity