← previous blocknext block →recent activity
Analyzing
Block #83,356,188
17 transactions · 15 stateful · 2026-06-24 09:18:27 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,356,188 · 17 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
1w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x18cbab19…7a73
0x34b655…2a6f
2 touches
0 conflicts
0x1f3ae3d2…5ad0
0x34b655…2a6f
2 touches
0 conflicts
0xf4c23949…9b02
0x34b655…2a6f
2 touches
0 conflicts
0x5a30d8a9…f768
0x34b655…2a6f
2 touches
0 conflicts
0x5d2b5661…df66
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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity