← previous blocknext block →recent activity
Analyzing
Block #81,480,526
20 transactions · 20 stateful · 2026-06-15 16:36:45 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,480,526 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w28w39w311w013w116w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xd7a3d42d…e766
0x40c49f…2af0
6 touches
3 conflicts
0x48acfd83…7ef0
0x40c49f…2af0
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x73131ffc…b46c
0x5df178…7777
6 touches
3 conflicts
0x00000000…0000
0x2c492d…444e
6 touches
3 conflicts
0x00000000…0001
0x2c492d…444e
6 touches
3 conflicts
0x44ad89ba…cf83
0x5df178…7777
6 touches
3 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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity