← previous blocknext block →recent activity
Analyzing
Block #81,634,368
14 transactions · 9 stateful · 2026-06-16 09:41:23 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,634,368 · 14 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
2w05w06w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d4584bf…d508
0x34b655…2a6f
6 touches
3 conflicts
0xd364a7f3…7fc6
0x2a68ba…90c5
4 touches
1 conflict
0xc0ee8ce1…0778
0x34b655…2a6f
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3ebaa251…978e
0x34b655…2a6f
4 touches
1 conflict
0x60d07066…695c
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
3 conflicts on slot 0x1d4584bfa9…e8d508
Audit this contract →
← previous block·next block →recent activity