← previous blocknext block →recent activity
Analyzing
Block #102,207,464
13 transactions · 13 stateful · 2026-09-05 14:23:32 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,207,464 · 13 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
1w02w15w07w18w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81f65578…8168
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x4a70f78c…d41a
0x34b655…2a6f
4 touches
1 conflict
0x79ec4509…1f61
0x34b655…2a6f
4 touches
1 conflict
0x7d6b9af1…9a38
0x34b655…2a6f
4 touches
1 conflict
0xfd713bab…a651
0x34b655…2a6f
4 touches
1 conflict
0x3167d7d8…a06b
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
6 conflicts on slot 0x81f65578f6…1f8168
Audit this contract →
← previous block·next block →recent activity