← previous blocknext block →recent activity
Analyzing
Block #80,642,203
25 transactions · 22 stateful · 2026-06-11 19:30:53 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,642,203 · 25 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
1w02w15w06w07w113w014w118w122w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc38151f2…2bcb
0xc8689a…ee79
4 touches
1 conflict
0x00000000…0002
0xb18bf8…e9f3
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity