← previous blocknext block →recent activity
Analyzing
Block #83,410,141
19 transactions · 16 stateful · 2026-06-24 15:19:03 UTC
Parallelism
79/100
Blocked
19%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,410,141 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w111w017w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4efb974a…6126
0x34b655…2a6f
8 touches
6 conflicts
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0xfc683d5e…46fa
0x34b655…2a6f
4 touches
1 conflict
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x1cfb2e47…606d
0x34b655…2a6f
4 touches
1 conflict
0x7b5dea55…ac96
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
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
6 conflicts on slot 0x4efb974ac9…0d6126
Audit this contract →
← previous block·next block →recent activity