← previous blocknext block →recent activity
Analyzing
Block #102,479,577
14 transactions · 13 stateful · 2026-09-06 13:22:09 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,479,577 · 14 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
1w02w13w09w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f6c4dd…22e3
0x34b655…2a6f
4 touches
1 conflict
0x01315072…0e2d
0x34b655…2a6f
4 touches
1 conflict
0x04d1844c…05dd
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x14b0fe41…2050
0x34b655…2a6f
4 touches
1 conflict
0x1513b999…b52e
0x34b655…2a6f
4 touches
1 conflict
0x21adef83…f2b7
0x34b655…2a6f
4 touches
1 conflict
0x29dbeafe…6ff7
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 0x00f6c4dd5d…7e22e3
Audit this contract →
← previous block·next block →recent activity