← previous blocknext block →recent activity
Analyzing
Block #81,879,308
26 transactions · 22 stateful · 2026-06-17 12:53:29 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,879,308 · 26 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
1w02w14w05w16w27w19w110w211w217w018w019w220w023w124w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3439dfbc…0d03
0x34b655…2a6f
8 touches
6 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x112cf8ad…6e4f
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x981e820d…ca8f
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
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
6 conflicts on slot 0x3439dfbcc6…080d03
Audit this contract →
← previous block·next block →recent activity