← previous blocknext block →recent activity
Analyzing
Block #102,252,492
16 transactions · 16 stateful · 2026-09-05 18:11:37 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,252,492 · 16 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
5w06w17w210w311w412w013w114w515w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9d11061…b7e9
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x316c3a9b…7302
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x044844a0…7418
0x34b655…2a6f
4 touches
1 conflict
0x24ed74ea…a3ff
0x34b655…2a6f
4 touches
1 conflict
0xc09c3422…3c8b
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
15 conflicts on slot 0xa9d110613e…d3b7e9
Audit this contract →
← previous block·next block →recent activity