← previous blocknext block →recent activity
Analyzing
Block #106,389,469
21 transactions · 19 stateful · 2026-09-20 06:17:11 UTC
Parallelism
86/100
Blocked
26%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,389,469 · 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
1w02w14w06w012w113w115w119w020w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17bb579f…938c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0xb8745f57…27c1
0x34b655…2a6f
4 touches
1 conflict
0xd8916bd7…6415
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x33253407…a2ff
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 0x17bb579f2c…21938c
Audit this contract →
← previous block·next block →recent activity