← previous blocknext block →recent activity
Analyzing
Block #106,921,750
20 transactions · 20 stateful · 2026-09-22 02:57:12 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,921,750 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w17w19w210w311w113w014w315w417w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ad1b8fb…00ec
0x34b655…2a6f
8 touches
6 conflicts
0x411222c5…925d
0x34b655…2a6f
8 touches
6 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x0747620e…9783
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x8ad1b8fb6a…3c00ec
Audit this contract →
← previous block·next block →recent activity