← previous blocknext block →recent activity
Analyzing
Block #81,479,736
30 transactions · 24 stateful · 2026-06-15 16:31:28 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,479,736 · 30 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
1w04w05w06w07w18w19w210w211w116w017w118w022w125w126w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda46b60e…4507
0x34b655…2a6f
8 touches
6 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
8 touches
6 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
6 touches
3 conflicts
0x2cd98078…527c
0x34b655…2a6f
6 touches
3 conflicts
0x3187fda9…57d9
0x34b655…2a6f
6 touches
3 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
6 touches
3 conflicts
0x4546ebad…b908
0x34b655…2a6f
6 touches
3 conflicts
0x4d3e58e0…a2d7
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 0xda46b60e4f…d44507
Audit this contract →
← previous block·next block →recent activity