← previous blocknext block →recent activity
Analyzing
Block #81,878,910
28 transactions · 16 stateful · 2026-06-17 12:50:49 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,878,910 · 28 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
3w04w110w014w015w116w217w318w219w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x503b3a72…f6df
0x34b655…2a6f
8 touches
6 conflicts
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
6 touches
3 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
6 touches
3 conflicts
0x826cce18…251c
0x34b655…2a6f
6 touches
3 conflicts
0x94be3d8a…76a3
0x34b655…2a6f
6 touches
3 conflicts
0xa72e521d…f873
0x34b655…2a6f
6 touches
3 conflicts
0xaf498679…7732
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x503b3a72dc…c4f6df
Audit this contract →
← previous block·next block →recent activity