← previous blocknext block →recent activity
Analyzing
Block #106,163,988
21 transactions · 21 stateful · 2026-09-19 11:22:21 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,163,988 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w19w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56d33275…c42f
0x34b655…2a6f
4 touches
1 conflict
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0388b848…5da6
0x34b655…2a6f
2 touches
0 conflicts
0x0ffac39e…6d34
0x34b655…2a6f
2 touches
0 conflicts
0x173b64af…6c43
0x34b655…2a6f
2 touches
0 conflicts
0x1b78cfed…e85d
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 0x56d33275b1…8cc42f
Audit this contract →
← previous block·next block →recent activity