← previous blocknext block →recent activity
Analyzing
Block #84,363,332
26 transactions · 22 stateful · 2026-06-29 01:14:33 UTC
Parallelism
81/100
Blocked
55%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,363,332 · 26 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
1w02w13w26w08w110w011w112w213w014w215w316w417w119w022w123w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44843215…109b
0x34b655…2a6f
8 touches
6 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0xde9ed66f…6fbe
0xd32edf…ff58
5 touches
3 conflicts
0xe75cebb6…6b36
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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 0x44843215c9…be109b
Audit this contract →
← previous block·next block →recent activity