← previous blocknext block →recent activity
Analyzing
Block #84,605,903
22 transactions · 20 stateful · 2026-06-30 04:12:17 UTC
Parallelism
77/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,605,903 · 22 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
2w03w18w09w117w018w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf98f45fd…37b1
0x34b655…2a6f
6 touches
3 conflicts
0x57be321f…fecc
0x34b655…2a6f
6 touches
3 conflicts
0x8b1b058b…0435
0x34b655…2a6f
6 touches
3 conflicts
0x344bc09a…942f
0x34b655…2a6f
4 touches
1 conflict
0x5761860a…8ebc
0x34b655…2a6f
4 touches
1 conflict
0x2060d8b9…a088
0x34b655…2a6f
4 touches
1 conflict
0x6af30fc9…7dd3
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity