← previous blocknext block →recent activity
Analyzing
Block #102,060,394
21 transactions · 21 stateful · 2026-09-05 01:57:52 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,060,394 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w012w015w116w217w218w119w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b13e91…855d
0x34b655…2a6f
6 touches
3 conflicts
0x124368e7…b95d
0x065c9d…c394
4 touches
1 conflict
0x625a90a7…b9ff
0x065c9d…c394
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x33b7fbba…64de
0x34b655…2a6f
4 touches
1 conflict
0x477cb4f5…11b4
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5dd033b6…34b5
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 0x91b13e914b…cb855d
Audit this contract →
← previous block·next block →recent activity