← previous blocknext block →recent activity
Analyzing
Block #81,617,164
24 transactions · 21 stateful · 2026-06-16 07:46:52 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #81,617,164 · 24 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
1w02w13w04w15w09w011w113w217w018w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x81e1f4e8…08d7
0x34b655…2a6f
6 touches
3 conflicts
0xb409e204…89ac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x65c50a7f…f491
0x34b655…2a6f
4 touches
1 conflict
0x7513257f…2749
0x34b655…2a6f
4 touches
1 conflict
0x80269196…b9e2
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity