← previous blocknext block →recent activity
Analyzing
Block #103,214,203
19 transactions · 17 stateful · 2026-09-09 03:09:39 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,214,203 · 19 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
1w02w110w211w313w314w315w417w018w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x754bbcbe…427e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xab612fbf…82c8
0x34b655…2a6f
6 touches
3 conflicts
0xd9722304…6ed0
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0505bae8…b4fb
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
6 conflicts on slot 0x754bbcbe52…67427e
Audit this contract →
← previous block·next block →recent activity