← previous blocknext block →recent activity
Analyzing
Block #81,631,153
24 transactions · 11 stateful · 2026-06-16 09:20:01 UTC
Parallelism
92/100
Blocked
9%
Avg conflicts / tx
0.04
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,631,153 · 24 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
3w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0869a723…09b8
0x1efe02…37d6
2 touches
0 conflicts
0xc52505dc…410c
0x1efe02…37d6
2 touches
0 conflicts
0xc9cea23c…29e5
0x1efe02…37d6
2 touches
0 conflicts
0xf298c368…a481
0x1efe02…37d6
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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: LeverUp: LeverUp
1 conflict on slot 0xb6b74ae0ff…d48d5e
Audit this contract →
← previous block·next block →recent activity