← previous blocknext block →recent activity
Analyzing
Block #84,192,864
28 transactions · 25 stateful · 2026-06-28 06:18:28 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,192,864 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w06w17w110w011w012w113w214w315w016w117w118w119w226w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
8 touches
6 conflicts
0xe75cebb6…6b36
0x065c9d…c394
6 touches
3 conflicts
0xab86573c…682e
0x34b655…2a6f
6 touches
3 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
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
0x00000000…001e
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: 0xd637b38f…c64160
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity