← previous blocknext block →recent activity
Analyzing
Block #84,304,948
20 transactions · 18 stateful · 2026-06-28 18:45:25 UTC
Parallelism
90/100
Blocked
17%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,304,948 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w110w012w115w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x7dc64b2c…05e7
0x34b655…2a6f
4 touches
1 conflict
0xd597209e…9800
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xb05cd4f5…73d0
0x69df8a…6292
2 touches
0 conflicts
0xdb067026…9eb8
0x69df8a…6292
2 touches
0 conflicts
0x00000000…003d
0xa6afd3…d132
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 0x4ec9ff52ce…67e6f7
Audit this contract →
← previous block·next block →recent activity