← previous blocknext block →recent activity
Analyzing
Block #83,492,963
7 transactions · 6 stateful · 2026-06-25 00:31:59 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,492,963 · 7 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x709c5c4c…bd35
0x34b655…2a6f
4 touches
1 conflict
0xb99958f6…ccf0
0x34b655…2a6f
4 touches
1 conflict
0xb99958f6…ccf1
0x34b655…2a6f
4 touches
1 conflict
0xadb7bbb1…8884
0x34b655…2a6f
3 touches
1 conflict
0x0e213495…6d39
0x34b655…2a6f
2 touches
0 conflicts
0x25de453d…9573
0x34b655…2a6f
2 touches
0 conflicts
0x3f7a8f08…ebb3
0x34b655…2a6f
2 touches
0 conflicts
0x53122a4f…f4d1
0x34b655…2a6f
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 0x709c5c4c86…c1bd35
Audit this contract →
← previous block·next block →recent activity