← previous blocknext block →recent activity
Analyzing
Block #81,617,061
19 transactions · 15 stateful · 2026-06-16 07:46:10 UTC
Parallelism
58/100
Blocked
47%
Avg conflicts / tx
1.79
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #81,617,061 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w112w013w214w315w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
10 touches
10 conflicts
0x2afe4dba…3b17
0x34b655…2a6f
8 touches
6 conflicts
0x3e505a15…70f8
0x34b655…2a6f
6 touches
3 conflicts
0x41be9e75…9773
0x34b655…2a6f
6 touches
3 conflicts
0x7e17e82a…9748
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
21 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity