← previous blocknext block →recent activity
Analyzing
Block #83,495,550
25 transactions · 21 stateful · 2026-06-25 00:49:10 UTC
Parallelism
84/100
Blocked
24%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,495,550 · 25 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
7w08w19w213w018w119w321w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x084b86f8…4a63
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x3817764d…242b
0x34b655…2a6f
6 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x39451527…ad86
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 0x084b86f841…8d4a63
Audit this contract →
← previous block·next block →recent activity