← previous blocknext block →recent activity
Analyzing
Block #102,061,022
30 transactions · 28 stateful · 2026-09-05 02:01:03 UTC
Parallelism
80/100
Blocked
54%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,061,022 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w06w18w09w110w211w312w416w122w023w124w225w326w327w328w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x1dc71894…1884
0x34b655…2a6f
6 touches
3 conflicts
0x42e5184f…4e8b
0x34b655…2a6f
6 touches
3 conflicts
0x9ff94a68…7ae8
0x34b655…2a6f
6 touches
3 conflicts
0xb74fe31e…a928
0x34b655…2a6f
6 touches
3 conflicts
0xbceecf11…0120
0x34b655…2a6f
6 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
10 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity