← previous blocknext block →recent activity
Analyzing
Block #81,618,839
14 transactions · 13 stateful · 2026-06-16 07:57:59 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,618,839 · 14 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
1w02w13w24w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf362e8a6…6ce6
0x851145…3f07
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x851145…3f07
8 touches
6 conflicts
0x6e733b13…b909
0x851145…3f07
6 touches
3 conflicts
0x0fde64da…aa3e
0x2a68ba…90c5
6 touches
3 conflicts
0x8d0d8061…d410
0xc8689a…ee79
6 touches
3 conflicts
0x7a12283f…b18a
0x69df8a…6292
6 touches
3 conflicts
0x915c095e…c1e5
0x69df8a…6292
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: 0x851145ea…9f3f07
6 conflicts on slot 0xf362e8a663…ea6ce6
Audit this contract →
← previous block·next block →recent activity