← previous blocknext block →recent activity
Analyzing
Block #93,234,288
22 transactions · 21 stateful · 2026-08-05 03:01:40 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,234,288 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w18w29w310w411w414w015w116w217w318w520w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0xb716463e…8336
0x968279…9342
8 touches
6 conflicts
0x3ca98e98…b0ae
0x968279…9342
8 touches
6 conflicts
0x3ca98e98…b0af
0x968279…9342
8 touches
6 conflicts
0x3ca98e98…b0b1
0x968279…9342
8 touches
6 conflicts
0xb716463e…832f
0x968279…9342
8 touches
6 conflicts
0xb716463e…8330
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: Perpl
10 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity