← previous blocknext block →recent activity
Analyzing
Block #103,213,727
21 transactions · 21 stateful · 2026-09-09 03:07:16 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #103,213,727 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w08w010w112w114w115w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x0fb116d3…6486
0x34b655…2a6f
6 touches
3 conflicts
0x18cf84a6…09e4
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0x2f17174f…68b4
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x3e7ad612…e804
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity