← previous blocknext block →recent activity
Analyzing
Block #102,382,760
19 transactions · 18 stateful · 2026-09-06 05:11:43 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,382,760 · 19 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
1w06w17w212w013w314w417w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c67d31e…3dbe
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x89656ac5…5173
0x34b655…2a6f
4 touches
1 conflict
0xbc7d5199…c05f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
3 conflicts on slot 0x3c67d31e03…f03dbe
Audit this contract →
← previous block·next block →recent activity