← previous blocknext block →recent activity
Analyzing
Block #83,400,871
18 transactions · 17 stateful · 2026-06-24 14:17:05 UTC
Parallelism
72/100
Blocked
59%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,400,871 · 18 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
1w02w13w24w05w06w17w28w39w412w013w114w216w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x2004b5f1…ff98
0x34b655…2a6f
4 touches
1 conflict
0x2ead2ab8…20b3
0x34b655…2a6f
4 touches
1 conflict
0x46762881…8a3e
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0x901d9f30…67a4
0x34b655…2a6f
4 touches
1 conflict
0x9603d13f…d632
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity