← previous blocknext block →recent activity
Analyzing
Block #102,283,714
13 transactions · 13 stateful · 2026-09-05 20:49:57 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,283,714 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w29w010w111w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0f6895c…e428
0x34b655…2a6f
6 touches
3 conflicts
0xd98afa6e…3364
0x34b655…2a6f
6 touches
3 conflicts
0x1513b999…b52e
0x34b655…2a6f
6 touches
3 conflicts
0xca544518…82c2
0x34b655…2a6f
6 touches
3 conflicts
0xc853be2d…b18f
0x34b655…2a6f
6 touches
3 conflicts
0x3d13406e…eff1
0x34b655…2a6f
6 touches
3 conflicts
0x477cb4f5…11b4
0x34b655…2a6f
6 touches
3 conflicts
0x4dffc33e…068d
0x34b655…2a6f
6 touches
3 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
3 conflicts on slot 0xc0f6895c5d…fee428
Audit this contract →
← previous block·next block →recent activity