← previous blocknext block →recent activity
Analyzing
Block #83,642,813
8 transactions · 6 stateful · 2026-06-25 17:11:57 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,642,813 · 8 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xeea925f1…dd64
0x34b655…2a6f
4 touches
1 conflict
0x44843215…109b
0x34b655…2a6f
4 touches
1 conflict
0xcde75077…ccee
0x34b655…2a6f
4 touches
1 conflict
0x2531931d…8bd1
0x34b655…2a6f
2 touches
0 conflicts
0x33244695…415f
0x34b655…2a6f
2 touches
0 conflicts
0x3a20ada1…53e1
0x34b655…2a6f
2 touches
0 conflicts
0x63a8e5e3…0135
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity