← previous blocknext block →recent activity
Analyzing
Block #80,844,186
12 transactions · 8 stateful · 2026-06-12 17:57:43 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,844,186 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0x7be3246e…f89f
0x34b655…2a6f
4 touches
1 conflict
0x3b9bb58c…e73a
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x004989aa…b35a
0x34b655…2a6f
2 touches
0 conflicts
0x281f1511…22cb
0x34b655…2a6f
2 touches
0 conflicts
0x30fb7484…5ccf
0x34b655…2a6f
2 touches
0 conflicts
0x49344f38…676d
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
1 conflict on slot 0x18978822b6…2c2623
Audit this contract →
← previous block·next block →recent activity