← previous blocknext block →recent activity
Analyzing
Block #102,174,003
16 transactions · 16 stateful · 2026-09-05 11:33:59 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,174,003 · 16 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
1w02w17w011w112w213w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92fa1dc0…b239
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xd5c17eae…a8a9
0x34b655…2a6f
6 touches
3 conflicts
0x6f4e7625…aba5
0x34b655…2a6f
6 touches
3 conflicts
0xec9030a2…0020
0x34b655…2a6f
6 touches
3 conflicts
0x786d66ce…ae70
0x34b655…2a6f
5 touches
3 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 0x92fa1dc002…a3b239
Audit this contract →
← previous block·next block →recent activity