← previous blocknext block →recent activity
Analyzing
Block #83,200,819
17 transactions · 13 stateful · 2026-06-23 16:00:36 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,200,819 · 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
13w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e505a15…70f8
0x34b655…2a6f
4 touches
1 conflict
0xa1571d54…ae41
0x34b655…2a6f
4 touches
1 conflict
0xa51de3df…c65a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x03890ac9…e802
0x34b655…2a6f
4 touches
1 conflict
0x672fd8ba…9e9e
0x34b655…2a6f
3 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
1 conflict on slot 0x3e505a15cf…0a70f8
Audit this contract →
← previous block·next block →recent activity