← previous blocknext block →recent activity
Analyzing
Block #81,878,216
18 transactions · 14 stateful · 2026-06-17 12:46:10 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,878,216 · 18 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
1w02w13w24w27w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeef70cb9…5de7
0xea1b8e…c5ec
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xd8eb2d31…2ac0
0xea1b8e…c5ec
6 touches
3 conflicts
0x9560013d…8caf
0xfd44b3…00d1
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9c8d6dd6…d61d
0xea1b8e…c5ec
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0xbc33a929…8b24
0xea1b8e…c5ec
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: LeverUp: LeverUp
3 conflicts on slot 0xeef70cb93b…ad5de7
Audit this contract →
← previous block·next block →recent activity