← previous blocknext block →recent activity
Analyzing
Block #80,267,040
19 transactions · 15 stateful · 2026-06-10 01:49:09 UTC
Parallelism
84/100
Blocked
27%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,267,040 · 19 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
1w02w13w214w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1da1c6cb…bb3f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa05f2e59…edac
0xd32edf…ff58
5 touches
3 conflicts
0x3293a887…43fd
0x1b6862…e19c
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x746bcce3…d0ce
0x34b655…2a6f
4 touches
1 conflict
0x8fb0fecf…cb2f
0x34b655…2a6f
4 touches
1 conflict
0x943e9fce…3cdb
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 0x1da1c6cbeb…31bb3f
Audit this contract →
← previous block·next block →recent activity