← previous blocknext block →recent activity
Analyzing
Block #92,348,857
19 transactions · 19 stateful · 2026-08-02 00:45:26 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,348,857 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w48w09w110w211w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0cbb4f7…234e
0x7b9256…1fb2
14 touches
21 conflicts
0xc0cbb4f7…234f
0x7b9256…1fb2
14 touches
21 conflicts
0x177211e2…1c2d
0x754704…b603
14 touches
21 conflicts
0xe1f61186…e2f8
0x754704…b603
14 touches
21 conflicts
0x00000000…0006
0x7b9256…1fb2
14 touches
21 conflicts
0x5921a85d…05a3
0x7b9256…1fb2
14 touches
21 conflicts
0x5921a85d…05a4
0x7b9256…1fb2
14 touches
21 conflicts
0x5921a85d…05a7
0x7b9256…1fb2
14 touches
21 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: 0x7b9256fd…e21fb2
21 conflicts on slot 0xc0cbb4f776…e3234e
Audit this contract →
← previous block·next block →recent activity