← previous blocknext block →recent activity
Analyzing
Block #84,041,267
21 transactions · 19 stateful · 2026-06-27 13:29:05 UTC
Parallelism
76/100
Blocked
37%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,041,267 · 21 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
1w02w14w09w010w011w114w015w117w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
6 touches
3 conflicts
0xa97a5eff…05ae
0x34b655…2a6f
6 touches
3 conflicts
0xd58b9a66…1c23
0x34b655…2a6f
6 touches
3 conflicts
0xe732567d…b65d
0x34b655…2a6f
6 touches
3 conflicts
0x7e17e82a…9748
0x34b655…2a6f
6 touches
3 conflicts
0x5ffc25fa…b119
0x34b655…2a6f
4 touches
1 conflict
0x60146498…2704
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity