← previous blocknext block →recent activity
Analyzing
Block #106,422,845
17 transactions · 16 stateful · 2026-09-20 09:05:08 UTC
Parallelism
59/100
Blocked
44%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,422,845 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w27w312w313w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4265984a…a7d2
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
4 touches
1 conflict
0x9708602e…de14
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb0f5d668…99ac
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
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 0x4265984a2d…00a7d2
Audit this contract →
← previous block·next block →recent activity