← previous blocknext block →recent activity
Analyzing
Block #106,954,363
20 transactions · 19 stateful · 2026-09-22 05:41:22 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,954,363 · 20 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
1w02w03w14w05w17w08w113w214w315w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01ad5dd0…11a1
0x34b655…2a6f
8 touches
6 conflicts
0xe7f1cb38…d377
0x34b655…2a6f
8 touches
6 conflicts
0x0bfb99f2…9779
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x73a0005f…70a8
0x34b655…2a6f
4 touches
1 conflict
0xab290f36…d824
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 0x01ad5dd035…5d11a1
Audit this contract →
← previous block·next block →recent activity