← previous blocknext block →recent activity
Analyzing
Block #106,373,034
9 transactions · 9 stateful · 2026-09-20 04:54:28 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,373,034 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6be05f69…33d9
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x07bd96b2…9e93
0x34b655…2a6f
2 touches
0 conflicts
0x08c5d8d8…c7c1
0x34b655…2a6f
2 touches
0 conflicts
0x102ab3ca…83b4
0x34b655…2a6f
2 touches
0 conflicts
0x12d7d328…0ffd
0x34b655…2a6f
2 touches
0 conflicts
0x2249932e…474a
0x34b655…2a6f
2 touches
0 conflicts
0x29a58269…011a
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x6be05f6972…0a33d9
Audit this contract →
← previous block·next block →recent activity