← previous blocknext block →recent activity
Analyzing
Block #81,627,985
10 transactions · 10 stateful · 2026-06-16 08:58:56 UTC
Parallelism
60/100
Blocked
30%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,627,985 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5d7e85d…b578
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x897df0ee…b0c5
0x40c49f…2af0
4 touches
1 conflict
0xa2b0bf20…71c6
0x40c49f…2af0
4 touches
1 conflict
0xd3631e6e…8fd0
0x40c49f…2af0
4 touches
1 conflict
0x0b6d70b7…cdec
0x40c49f…2af0
2 touches
0 conflicts
0x213ee207…a151
0x69df8a…6292
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: 0x40c49f17…d22af0
3 conflicts on slot 0xc5d7e85db7…01b578
Audit this contract →
← previous block·next block →recent activity