← previous blocknext block →recent activity
Analyzing
Block #106,932,537
16 transactions · 16 stateful · 2026-09-22 03:51:30 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.25
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,932,537 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w28w39w410w511w612w714w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46483cb1…e7ca
0x34b655…2a6f
10 touches
10 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0xedfd12b0…dba4
0x34b655…2a6f
8 touches
6 conflicts
0x14b80268…69ef
0x34b655…2a6f
8 touches
6 conflicts
0x858e40c0…7e30
0x34b655…2a6f
4 touches
1 conflict
0x3c82c97a…8833
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
10 conflicts on slot 0x46483cb14f…c1e7ca
Audit this contract →
← previous block·next block →recent activity