← previous blocknext block →recent activity
Analyzing
Block #80,742,643
71 transactions · 11 stateful · 2026-06-12 06:40:30 UTC
Parallelism
97/100
Blocked
9%
Avg conflicts / tx
0.01
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,742,643 · 71 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
69w070w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x256ef834…e8ed
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
2 touches
0 conflicts
0x2c9bf20d…f42b
0x34b655…2a6f
2 touches
0 conflicts
0x2ef0dd18…b5e6
0x34b655…2a6f
2 touches
0 conflicts
0x4acc1f31…9942
0x34b655…2a6f
2 touches
0 conflicts
0x53b4ef2b…8a05
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity