← previous blocknext block →recent activity
Analyzing
Block #80,257,949
12 transactions · 9 stateful · 2026-06-10 00:48:29 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,257,949 · 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
1w02w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0462262d…a368
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xb5fd96f7…10c8
0x065c9d…c394
2 touches
0 conflicts
0x0c0048db…1a25
0x2a68ba…90c5
2 touches
0 conflicts
0xe60a628c…d6d7
0x2a68ba…90c5
2 touches
0 conflicts
0x6674247f…5745
0x699abc…6a3b
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 0x0462262d7c…7ea368
Audit this contract →
← previous block·next block →recent activity