← previous blocknext block →recent activity
Analyzing
Block #83,494,324
11 transactions · 10 stateful · 2026-06-25 00:41:03 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,494,324 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x571cb36d…3b3d
0x34b655…2a6f
4 touches
1 conflict
0xd2453506…54e4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x66a57cb3…11d8
0x754704…b603
2 touches
0 conflicts
0xaafb3ccc…eacf
0xad96c3…8d7c
2 touches
0 conflicts
0xbdd29ea9…58be
0xad96c3…8d7c
2 touches
0 conflicts
0x00000000…00a6
0xbb4738…ed6c
2 touches
0 conflicts
0x00000000…00a7
0xbb4738…ed6c
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 0x571cb36db3…a33b3d
Audit this contract →
← previous block·next block →recent activity