← previous blocknext block →recent activity
Analyzing
Block #83,643,029
14 transactions · 13 stateful · 2026-06-25 17:13:23 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
1.21
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,643,029 · 14 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
3w04w15w28w09w210w312w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b61212e…558e
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x403d1735…de44
0x34b655…2a6f
6 touches
3 conflicts
0xed3b3567…3c8e
0x34b655…2a6f
6 touches
3 conflicts
0xb757d20e…7cc3
0x34b655…2a6f
6 touches
3 conflicts
0x88f49da5…2586
0x34b655…2a6f
4 touches
1 conflict
0x9b58e20f…2dd9
0x34b655…2a6f
4 touches
1 conflict
0xa80684c9…3948
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 0x8b61212ee1…d1558e
Audit this contract →
← previous block·next block →recent activity