← previous blocknext block →recent activity
Analyzing
Block #103,214,662
18 transactions · 17 stateful · 2026-09-09 03:11:59 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,214,662 · 18 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
2w07w012w014w115w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x040e9d01…7076
0x34b655…2a6f
2 touches
0 conflicts
0x0437fafe…74d0
0x34b655…2a6f
2 touches
0 conflicts
0x05870129…4a57
0x34b655…2a6f
2 touches
0 conflicts
0x17d767b2…0f7d
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity