← previous blocknext block →recent activity
Analyzing
Block #80,823,516
27 transactions · 20 stateful · 2026-06-12 15:39:46 UTC
Parallelism
89/100
Blocked
35%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,823,516 · 27 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
1w02w13w09w210w113w016w118w020w021w124w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xb9580567…444f
0x8fbe07…71b6
4 touches
1 conflict
0x8ab0fc5e…694e
0x065c9d…c394
4 touches
1 conflict
0x00000000…000b
0x772635…0b37
4 touches
1 conflict
0x48c8e9a4…6fae
0x065c9d…c394
3 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity