← previous blocknext block →recent activity
Analyzing
Block #102,137,858
24 transactions · 15 stateful · 2026-09-05 08:30:42 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,137,858 · 24 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
4w05w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0dc2aef…ea3e
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8e31e8e8…a6aa
0x34b655…2a6f
4 touches
1 conflict
0x588380ee…0a5c
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x939cdd56…00c8
0x34b655…2a6f
4 touches
1 conflict
0xd5c98027…9fd9
0x34b655…2a6f
2 touches
0 conflicts
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 0xa0dc2aef0d…efea3e
Audit this contract →
← previous block·next block →recent activity