← previous blocknext block →recent activity
Analyzing
Block #102,079,245
13 transactions · 12 stateful · 2026-09-05 03:33:36 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,079,245 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5d28bce…c32c
0x34b655…2a6f
4 touches
1 conflict
0xac27d4e9…fffc
0x34b655…2a6f
4 touches
1 conflict
0xe6875750…9542
0x34b655…2a6f
4 touches
1 conflict
0xeb4304a5…dd06
0x34b655…2a6f
4 touches
1 conflict
0x01315072…0e2d
0x34b655…2a6f
4 touches
1 conflict
0x1513b999…b52e
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x4dffc33e…068d
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