← previous blocknext block →recent activity
Analyzing
Block #83,933,796
14 transactions · 11 stateful · 2026-06-27 01:32:58 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,933,796 · 14 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
5w06w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0020cef4…3ffc
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x6b47245e…a342
0x34b655…2a6f
4 touches
1 conflict
0x51ae5a4b…935e
0x34b655…2a6f
3 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
2 touches
0 conflicts
0x651411c9…66a9
0x34b655…2a6f
2 touches
0 conflicts
0x785889c9…0603
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 0x0020cef4ef…203ffc
Audit this contract →
← previous block·next block →recent activity