← previous blocknext block →recent activity
Analyzing
Block #81,880,858
20 transactions · 14 stateful · 2026-06-17 13:03:50 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,880,858 · 20 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
2w03w19w010w114w115w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3383813…4a0c
0x34b655…2a6f
6 touches
3 conflicts
0xb68e226d…c054
0xa6afd3…d132
4 touches
1 conflict
0xb6bc6efb…ad9b
0x34b655…2a6f
4 touches
1 conflict
0xc19d196a…e6be
0x34b655…2a6f
4 touches
1 conflict
0xcc1474f5…41f1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfb31d278…9107
0x34b655…2a6f
4 touches
1 conflict
0xfefb0189…f726
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 0xf338381336…ec4a0c
Audit this contract →
← previous block·next block →recent activity