← previous blocknext block →recent activity
Analyzing
Block #81,878,275
16 transactions · 14 stateful · 2026-06-17 12:46:34 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,878,275 · 16 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
1w02w03w04w15w211w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd4227d4…c28d
0x34b655…2a6f
7 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0xa7396f51…7f2f
0x34b655…2a6f
5 touches
3 conflicts
0x9092da13…341b
0x34b655…2a6f
4 touches
2 conflicts
0x5eeea918…8147
0x34b655…2a6f
4 touches
1 conflict
0x77581d05…90d5
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xcd4227d49b…1bc28d
Audit this contract →
← previous block·next block →recent activity