← previous blocknext block →recent activity
Analyzing
Block #83,951,487
23 transactions · 20 stateful · 2026-06-27 03:30:56 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,951,487 · 23 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
1w02w13w26w27w315w416w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc5f346…7b42
0x40c49f…2af0
6 touches
3 conflicts
0xe7b48dea…cf93
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x5a3732cb…edad
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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: 0x40c49f17…d22af0
3 conflicts on slot 0xdfc5f34630…0b7b42
Audit this contract →
← previous block·next block →recent activity