← previous blocknext block →recent activity
Analyzing
Block #105,922,176
37 transactions · 30 stateful · 2026-09-18 15:05:12 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.49
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,922,176 · 37 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
1w02w13w04w15w26w311w012w116w018w124w227w329w330w431w336w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0de7749d…5bef
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x86cea35b…bdff
0x34b655…2a6f
6 touches
3 conflicts
0x151fc7d7…3a62
0x34b655…2a6f
4 touches
1 conflict
0x16a8cd0c…27bd
0x34b655…2a6f
4 touches
1 conflict
0x191c54df…01c3
0x34b655…2a6f
4 touches
1 conflict
0x23b2399c…6e4b
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 0x0de7749d55…5c5bef
Audit this contract →
← previous block·next block →recent activity