← previous blocknext block →recent activity
Analyzing
Block #83,847,053
23 transactions · 19 stateful · 2026-06-26 15:54:39 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,847,053 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w112w013w214w015w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f2f9e67…3be0
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xb05cd4f5…73d0
0x69df8a…6292
2 touches
0 conflicts
0xdb067026…9eb8
0x69df8a…6292
2 touches
0 conflicts
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
1 conflict on slot 0x8f2f9e67ec…4f3be0
Audit this contract →
← previous block·next block →recent activity