← previous blocknext block →recent activity
Analyzing
Block #102,532,505
21 transactions · 16 stateful · 2026-09-06 17:50:38 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,532,505 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w113w214w015w116w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe20af769…5fea
0x34b655…2a6f
6 touches
3 conflicts
0x8e5690a1…89f0
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
4 touches
1 conflict
0x11db128b…1153
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x3b5fbc7d…c8fe
0x34b655…2a6f
4 touches
1 conflict
0x5fc0e620…7ee8
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 0xe20af7696b…f15fea
Audit this contract →
← previous block·next block →recent activity