← previous blocknext block →recent activity
Analyzing
Block #80,264,587
16 transactions · 11 stateful · 2026-06-10 01:32:47 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,264,587 · 16 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
1w02w13w16w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x080ca4e8…d573
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x9bd62ea7…b185
0x065c9d…c394
4 touches
1 conflict
0x6822257f…5601
0x34b655…2a6f
4 touches
1 conflict
0xb138d087…4689
0x34b655…2a6f
4 touches
1 conflict
0x5f0bee64…2407
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
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 0x080ca4e8e8…7dd573
Audit this contract →
← previous block·next block →recent activity