← previous blocknext block →recent activity
Analyzing
Block #81,617,201
14 transactions · 11 stateful · 2026-06-16 07:47:07 UTC
Parallelism
86/100
Blocked
9%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,617,201 · 14 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
2w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7d05530c…02d2
0x34b655…2a6f
4 touches
1 conflict
0xee8b3d20…00ff
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x16b4b48e…6a3e
0x065c9d…c394
2 touches
0 conflicts
0x30e301c2…8856
0x065c9d…c394
2 touches
0 conflicts
0x35d5fb2a…7214
0x065c9d…c394
2 touches
0 conflicts
0x795c30bd…d4c5
0x065c9d…c394
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity