← previous blocknext block →recent activity
Analyzing
Block #82,696,492
8 transactions · 6 stateful · 2026-06-21 07:49:36 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,696,492 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x588da1c1…6ae5
0x34b655…2a6f
4 touches
1 conflict
0x62db95d4…351c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd45bf713…49a6
0x34b655…2a6f
3 touches
1 conflict
0x98f98c7d…483b
0x0a4fcb…a602
2 touches
0 conflicts
0xac82bedb…0b9a
0x0a4fcb…a602
2 touches
0 conflicts
0xac82bedb…0b9e
0x0a4fcb…a602
2 touches
0 conflicts
0xac82bedb…0b9f
0x0a4fcb…a602
2 touches
0 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
1 conflict on slot 0x588da1c18d…a86ae5
Audit this contract →
← previous block·next block →recent activity