← previous blocknext block →recent activity
Analyzing
Block #80,823,529
43 transactions · 21 stateful · 2026-06-12 15:39:51 UTC
Parallelism
93/100
Blocked
29%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,823,529 · 43 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
4w05w16w08w19w011w017w018w119w020w122w140w041w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc575f8d…589a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x4d42f16e…a6c9
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0f6b6c51…f253
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
3 conflicts on slot 0xbc575f8d3e…12589a
Audit this contract →
← previous block·next block →recent activity