← previous blocknext block →recent activity
Analyzing
Block #92,856,402
17 transactions · 16 stateful · 2026-08-03 19:19:35 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,856,402 · 17 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
1w02w15w06w18w09w110w211w312w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9b555eb…25ec
0x968279…9342
8 touches
6 conflicts
0x521a5982…a82a
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0xaa6cc13d…62b7
0x968279…9342
8 touches
6 conflicts
0xaa6cc13d…62b8
0x968279…9342
8 touches
6 conflicts
0xaa6cc13d…62bb
0x968279…9342
8 touches
6 conflicts
0xaa6cc13d…62bc
0x968279…9342
8 touches
6 conflicts
0xaa6cc13d…62be
0x968279…9342
8 touches
6 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: 0x96827978…f09342
6 conflicts on slot 0xc9b555eb68…9525ec
Audit this contract →
← previous block·next block →recent activity