← previous blocknext block →recent activity
Analyzing
Block #106,381,401
15 transactions · 14 stateful · 2026-09-20 05:36:34 UTC
Parallelism
73/100
Blocked
21%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,381,401 · 15 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
1w02w17w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40c584a0…3f07
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x57b4d92f…8a5b
0x34b655…2a6f
5 touches
3 conflicts
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0x7fe8b5d8…3e49
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
3 conflicts on slot 0x40c584a0fc…ad3f07
Audit this contract →
← previous block·next block →recent activity