← previous blocknext block →recent activity
Analyzing
Block #106,234,973
32 transactions · 28 stateful · 2026-09-19 17:19:42 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,234,973 · 32 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
1w03w04w15w16w211w116w017w118w320w023w024w126w027w128w230w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3ed5a09…c6d3
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x4f42f0e5…dfd2
0x34b655…2a6f
4 touches
1 conflict
0x784f870c…0bfb
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a1
0x34b655…2a6f
4 touches
1 conflict
0xa6464996…3af9
0x34b655…2a6f
4 touches
1 conflict
0xb0e1ec3a…aa94
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 0xa3ed5a0966…25c6d3
Audit this contract →
← previous block·next block →recent activity