← previous blocknext block →recent activity
Analyzing
Block #84,577,448
8 transactions · 7 stateful · 2026-06-30 01:02:39 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,577,448 · 8 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
2w03w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x7f93f2f0…6666
0x34b655…2a6f
3 touches
1 conflict
0x042801a7…87c4
0x34b655…2a6f
2 touches
0 conflicts
0x1bcc5a7b…8af8
0x34b655…2a6f
2 touches
0 conflicts
0x3149127f…19a9
0x34b655…2a6f
2 touches
0 conflicts
0x374fc18a…6998
0x34b655…2a6f
2 touches
0 conflicts
0x414ddffd…e8c8
0x34b655…2a6f
2 touches
0 conflicts
0x44b331cd…eb25
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity