← previous blocknext block →recent activity
Analyzing
Block #84,354,021
18 transactions · 14 stateful · 2026-06-29 00:12:26 UTC
Parallelism
89/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,354,021 · 18 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
1w02w13w110w011w013w014w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0xf1b8c26d…5189
0x34b655…2a6f
4 touches
1 conflict
0x0c3040f0…6540
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
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
1 conflict on slot 0xab86573c9c…f3682e
Audit this contract →
← previous block·next block →recent activity