← previous blocknext block →recent activity
Analyzing
Block #106,154,929
20 transactions · 19 stateful · 2026-09-19 10:36:46 UTC
Parallelism
85/100
Blocked
16%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,154,929 · 20 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
2w03w111w015w118w019w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x13f8a428…1727
0x34b655…2a6f
4 touches
1 conflict
0x14f0a886…05ca
0x34b655…2a6f
4 touches
1 conflict
0x224fd185…dbb9
0x34b655…2a6f
4 touches
1 conflict
0x44f2bd3c…f875
0x34b655…2a6f
4 touches
1 conflict
0x5f749304…d1c1
0x34b655…2a6f
4 touches
1 conflict
0x60ffc0ea…6a07
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
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
1 conflict on slot 0x0ec07cf780…9cc0c9
Audit this contract →
← previous block·next block →recent activity