← previous blocknext block →recent activity
Analyzing
Block #106,030,842
20 transactions · 20 stateful · 2026-09-19 00:12:17 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,030,842 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w17w212w116w217w318w019w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48828733…fd48
0x34b655…2a6f
8 touches
6 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x12e77486…ec2b
0x34b655…2a6f
6 touches
3 conflicts
0x1a4b4833…cf01
0x34b655…2a6f
6 touches
3 conflicts
0x26253352…1a75
0x34b655…2a6f
6 touches
3 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
6 touches
3 conflicts
0x3b65c5ca…9f83
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
6 conflicts on slot 0x488287332c…96fd48
Audit this contract →
← previous block·next block →recent activity