← previous blocknext block →recent activity
Analyzing
Block #83,410,231
23 transactions · 22 stateful · 2026-06-24 15:19:40 UTC
Parallelism
78/100
Blocked
45%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,410,231 · 23 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
1w02w13w14w05w17w08w19w213w214w015w118w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x604d1daf…bf48
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe155a04c…f267
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x4efb974a…6126
0x34b655…2a6f
6 touches
3 conflicts
0x73912233…4589
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
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 0x604d1dafd7…a4bf48
Audit this contract →
← previous block·next block →recent activity