← previous blocknext block →recent activity
Analyzing
Block #83,467,268
17 transactions · 15 stateful · 2026-06-24 21:40:40 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,467,268 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w09w110w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50de69c5…dbbe
0x34b655…2a6f
6 touches
3 conflicts
0x6ac6d1bf…8b19
0x34b655…2a6f
6 touches
3 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x213a54fa…c85f
0x34b655…2a6f
6 touches
3 conflicts
0x24afc70d…36ef
0x34b655…2a6f
6 touches
3 conflicts
0x89fa3104…8020
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
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
3 conflicts on slot 0x50de69c5f6…08dbbe
Audit this contract →
← previous block·next block →recent activity