← previous blocknext block →recent activity
Analyzing
Block #84,037,813
10 transactions · 9 stateful · 2026-06-27 13:06:03 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,037,813 · 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
1w03w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf33e4b5b…f860
0x34b655…2a6f
4 touches
1 conflict
0xf33e4b5b…f861
0x34b655…2a6f
4 touches
1 conflict
0x581b829b…9578
0x34b655…2a6f
2 touches
0 conflicts
0x61c58a1f…e6b1
0x34b655…2a6f
2 touches
0 conflicts
0xbafbb974…c9e4
0x34b655…2a6f
2 touches
0 conflicts
0xc824469a…6425
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 0x18978822b6…2c2623
Audit this contract →
← previous block·next block →recent activity