← previous blocknext block →recent activity
Analyzing
Block #106,548,556
15 transactions · 15 stateful · 2026-09-20 19:37:53 UTC
Parallelism
47/100
Blocked
47%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,548,556 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w411w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46a5d79e…3d63
0x34b655…2a6f
12 touches
15 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
8 touches
6 conflicts
0x67a56c8b…f955
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x32aab5b0…0e4f
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x5906754f…b584
0x34b655…2a6f
8 touches
6 conflicts
0xd911522b…e960
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x46a5d79e43…cd3d63
Audit this contract →
← previous block·next block →recent activity