← previous blocknext block →recent activity
Analyzing
Block #83,635,974
21 transactions · 19 stateful · 2026-06-25 16:26:17 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,635,974 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w212w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd5d0a749…c426
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x021d9f75…6346
0x34b655…2a6f
4 touches
1 conflict
0x10bbcfd6…fee1
0x34b655…2a6f
4 touches
1 conflict
0x682ee7d2…a102
0x34b655…2a6f
4 touches
1 conflict
0x8802094b…3402
0x34b655…2a6f
4 touches
1 conflict
0x8ad0ae9d…a19f
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity