← previous blocknext block →recent activity
Analyzing
Block #103,211,784
9 transactions · 9 stateful · 2026-09-09 02:57:29 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,211,784 · 9 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
5w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e69ed1f…5d45
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x5c3a07bd…7c04
0x34b655…2a6f
4 touches
1 conflict
0x7729d2c9…8c22
0x34b655…2a6f
4 touches
1 conflict
0x7729d2c9…8c23
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf5da0c72…aa91
0x34b655…2a6f
3 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 0x1e69ed1f1c…335d45
Audit this contract →
← previous block·next block →recent activity