← previous blocknext block →recent activity
Analyzing
Block #83,625,448
28 transactions · 21 stateful · 2026-06-25 15:15:54 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,625,448 · 28 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
2w04w05w16w17w08w19w213w014w115w219w025w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xaa7ee7…f0e4
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x3506d730…fafd
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x8190162b…5c4b
0x34b655…2a6f
4 touches
1 conflict
0x9c4bf061…1101
0x34b655…2a6f
4 touches
1 conflict
0xa51de3df…c65a
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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity