← previous blocknext block →recent activity
Analyzing
Block #106,154,894
24 transactions · 23 stateful · 2026-09-19 10:36:35 UTC
Parallelism
88/100
Blocked
30%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,154,894 · 24 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
1w02w03w14w25w07w18w012w115w119w021w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x469dfc47…2886
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5c7b5ec0…0764
0x34b655…2a6f
4 touches
1 conflict
0x631454cd…d776
0x34b655…2a6f
4 touches
1 conflict
0x83a1e8d7…fe3f
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x8d616e7c…a6a1
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