← previous blocknext block →recent activity
Analyzing
Block #107,444,407
29 transactions · 27 stateful · 2026-09-23 22:48:22 UTC
Parallelism
86/100
Blocked
37%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,444,407 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w08w09w117w018w119w220w321w122w023w124w225w327w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x660b6e4f…3d72
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x27909bb7…b461
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x5060cdde…445d
0x34b655…2a6f
4 touches
1 conflict
0x999fd335…df7d
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
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 0x660b6e4ff5…403d72
Audit this contract →
← previous block·next block →recent activity