← previous blocknext block →recent activity
Analyzing
Block #102,312,957
14 transactions · 13 stateful · 2026-09-05 23:18:03 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,312,957 · 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
1w03w04w16w07w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb8f427f…f9a5
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x820d7282…6c34
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x36639c6b…4d00
0x34b655…2a6f
3 touches
1 conflict
0x4854b070…fb81
0x34b655…2a6f
3 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 0xfb8f427f74…c9f9a5
Audit this contract →
← previous block·next block →recent activity