← previous blocknext block →recent activity
Analyzing
Block #106,934,232
33 transactions · 31 stateful · 2026-09-22 04:00:02 UTC
Parallelism
85/100
Blocked
55%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,934,232 · 33 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
1w02w03w04w15w16w07w18w29w111w112w214w315w416w017w118w219w323w024w027w228w330w131w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x715eeec8…5664
0x34b655…2a6f
8 touches
6 conflicts
0x85bfd0af…ce96
0x34b655…2a6f
8 touches
6 conflicts
0xa9988419…9f45
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x810a3aa2…0227
0x34b655…2a6f
4 touches
1 conflict
0x839c0c71…bada
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 0x715eeec877…cd5664
Audit this contract →
← previous block·next block →recent activity