← previous blocknext block →recent activity
Analyzing
Block #83,637,029
30 transactions · 27 stateful · 2026-06-25 16:33:20 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,637,029 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w27w08w19w010w111w014w215w316w117w418w520w021w122w225w126w027w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf997c4c7…617d
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xe01158fd…f97f
0x1b6862…e19c
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xa3053ce8…c72a
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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 0xf997c4c76f…f2617d
Audit this contract →
← previous block·next block →recent activity