← previous blocknext block →recent activity
Analyzing
Block #102,394,864
13 transactions · 12 stateful · 2026-09-06 06:12:58 UTC
Parallelism
62/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,394,864 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w19w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5150abbe…43c3
0x34b655…2a6f
6 touches
3 conflicts
0x53c41998…7d52
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd435d60e…3eda
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x1139b3b1…daf2
0x34b655…2a6f
4 touches
1 conflict
0x5f251b96…6054
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 0x5150abbe56…e443c3
Audit this contract →
← previous block·next block →recent activity