← previous blocknext block →recent activity
Analyzing
Block #83,398,846
26 transactions · 17 stateful · 2026-06-24 14:03:33 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,398,846 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w114w015w116w219w123w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f2daaf7…f9e7
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0376b2da…e3af
0x34b655…2a6f
4 touches
1 conflict
0x9b3e3f59…b98f
0x34b655…2a6f
4 touches
1 conflict
0xa02e5cdd…76b8
0x34b655…2a6f
4 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
3 conflicts on slot 0x4f2daaf776…96f9e7
Audit this contract →
← previous block·next block →recent activity