← previous blocknext block →recent activity
Analyzing
Block #103,221,016
18 transactions · 15 stateful · 2026-09-09 03:44:00 UTC
Parallelism
89/100
Blocked
27%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,221,016 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w08w19w112w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9722304…6ed0
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x448fdf2a…fab4
0x34b655…2a6f
2 touches
0 conflicts
0x6dc1811e…2588
0x34b655…2a6f
2 touches
0 conflicts
0x7fd951f1…fe49
0x34b655…2a6f
2 touches
0 conflicts
0x87b41dd5…b410
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
1 conflict on slot 0xd97223041d…366ed0
Audit this contract →
← previous block·next block →recent activity