← previous blocknext block →recent activity
Analyzing
Block #84,576,290
10 transactions · 9 stateful · 2026-06-30 00:54:55 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,576,290 · 10 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
1w02w13w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xeaced15b…2221
0x754704…b603
4 touches
1 conflict
0xc4e19ae4…0788
0xe7cd86…c82d
4 touches
1 conflict
0x25de453d…9573
0x34b655…2a6f
2 touches
0 conflicts
0x46c7e43d…54dd
0x34b655…2a6f
2 touches
0 conflicts
0x5e87912c…7836
0x34b655…2a6f
2 touches
0 conflicts
0x67fc285e…2584
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity