← previous blocknext block →recent activity
Analyzing
Block #102,018,874
13 transactions · 13 stateful · 2026-09-04 22:27:34 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,018,874 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc852b267…9d14
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcc8b6d32…6601
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x165fe1f0…859f
0x34b655…2a6f
2 touches
0 conflicts
0x20b94f7c…2a9b
0x34b655…2a6f
2 touches
0 conflicts
0x247cfb80…cca8
0x34b655…2a6f
2 touches
0 conflicts
0x3bc232cc…9304
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
1 conflict on slot 0xc852b26715…339d14
Audit this contract →
← previous block·next block →recent activity