← previous blocknext block →recent activity
Analyzing
Block #80,124,927
21 transactions · 16 stateful · 2026-06-09 10:01:34 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,124,927 · 21 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
2w03w16w08w09w111w119w020w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67b7f565…0017
0x34b655…2a6f
6 touches
3 conflicts
0xcdc8b4bb…7bce
0x34b655…2a6f
6 touches
3 conflicts
0xc38151f2…2bcb
0xc8689a…ee79
4 touches
1 conflict
0x7895a98c…bbfa
0x34b655…2a6f
4 touches
1 conflict
0x8db1e0f2…2fcf
0x34b655…2a6f
4 touches
1 conflict
0x908d4442…2c4b
0x34b655…2a6f
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
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 0x67b7f565da…c60017
Audit this contract →
← previous block·next block →recent activity