← previous blocknext block →recent activity
Analyzing
Block #103,215,567
29 transactions · 26 stateful · 2026-09-09 03:16:32 UTC
Parallelism
90/100
Blocked
19%
Avg conflicts / tx
0.34
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,215,567 · 29 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
1w02w05w07w110w012w014w117w118w227w028w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c68d10b…8386
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1f396cee…862f
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x422d5490…52d9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6a9e408e…3721
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
3 conflicts on slot 0x7c68d10b83…628386
Audit this contract →
← previous block·next block →recent activity