← previous blocknext block →recent activity
Analyzing
Block #106,538,052
32 transactions · 30 stateful · 2026-09-20 18:45:01 UTC
Parallelism
84/100
Blocked
17%
Avg conflicts / tx
0.28
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,538,052 · 32 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
1w03w17w08w129w230w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xe7826b5b…166a
0x34b655…2a6f
4 touches
1 conflict
0x6d426cdf…360c
0x34b655…2a6f
4 touches
1 conflict
0x6d426cdf…360d
0x34b655…2a6f
4 touches
1 conflict
0x8d89de24…dec3
0x34b655…2a6f
4 touches
1 conflict
0xa1901e23…4027
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity