← previous blocknext block →recent activity
Analyzing
Block #102,059,402
17 transactions · 17 stateful · 2026-09-05 01:52:52 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,059,402 · 17 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
2w03w14w26w07w112w013w114w215w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdbcbb1e…b5d2
0x34b655…2a6f
6 touches
3 conflicts
0xdb8288e3…7979
0x34b655…2a6f
6 touches
3 conflicts
0x45ca01fd…8e75
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x42cda580…1baa
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x55a9172f…dae2
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
3 conflicts on slot 0xcdbcbb1e6e…68b5d2
Audit this contract →
← previous block·next block →recent activity