← previous blocknext block →recent activity
Analyzing
Block #103,211,827
13 transactions · 8 stateful · 2026-09-09 02:57:42 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,211,827 · 13 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
1w02w13w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5d28bce…c32c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x040e9d01…7076
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x1513b999…b52e
0x34b655…2a6f
4 touches
1 conflict
0x36aa792c…a68d
0x34b655…2a6f
4 touches
1 conflict
0x477cb4f5…11b4
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
1 conflict on slot 0xf5d28bce28…fbc32c
Audit this contract →
← previous block·next block →recent activity