← previous blocknext block →recent activity
Analyzing
Block #93,267,289
16 transactions · 16 stateful · 2026-08-05 05:47:36 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,267,289 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w08w19w210w311w413w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf48a8c63…0b01
0x968279…9342
10 touches
10 conflicts
0x521a5982…a82a
0x754704…b603
10 touches
10 conflicts
0x00000000…0006
0x968279…9342
10 touches
10 conflicts
0xce72ece5…88d1
0x968279…9342
10 touches
10 conflicts
0xce72ece5…88d2
0x968279…9342
10 touches
10 conflicts
0xce72ece5…88d4
0x968279…9342
10 touches
10 conflicts
0xf48a8c63…0afb
0x968279…9342
10 touches
10 conflicts
0xf48a8c63…0afc
0x968279…9342
10 touches
10 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
10 conflicts on slot 0xf48a8c630c…d20b01
Audit this contract →
← previous block·next block →recent activity