← previous blocknext block →recent activity
Analyzing
Block #83,638,904
16 transactions · 16 stateful · 2026-06-25 16:45:51 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,638,904 · 16 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
3w04w18w010w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x049cca71…b102
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
2 touches
0 conflicts
0x138e35f9…354e
0x34b655…2a6f
2 touches
0 conflicts
0x311fb479…2519
0x34b655…2a6f
2 touches
0 conflicts
0x320850c4…8643
0x34b655…2a6f
2 touches
0 conflicts
0x6d1160ba…890a
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 0x793aa64d0d…fdb09d
Audit this contract →
← previous block·next block →recent activity