← previous blocknext block →recent activity
Analyzing
Block #102,218,905
21 transactions · 21 stateful · 2026-09-05 15:21:26 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,218,905 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w19w210w315w416w517w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb38b444a…f83c
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xe108b282…58b3
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x513b0c80…d2d9
0x34b655…2a6f
4 touches
1 conflict
0x6636a104…d595
0x34b655…2a6f
4 touches
1 conflict
0x731d7308…fd26
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 0xb38b444a1c…1ef83c
Audit this contract →
← previous block·next block →recent activity