← previous blocknext block →recent activity
Analyzing
Block #80,484,327
13 transactions · 11 stateful · 2026-06-11 01:57:07 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,484,327 · 13 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
3w04w05w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa281ee2a…e417
0x96b79e…d00a
4 touches
1 conflict
0x1fc2d175…1d38
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0x93cd8311…e2a3
0x065c9d…c394
2 touches
0 conflicts
0xbf20ae88…a8b7
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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: 0x96b79ef4…d2d00a
1 conflict on slot 0xa281ee2a1b…66e417
Audit this contract →
← previous block·next block →recent activity