← previous blocknext block →recent activity
Analyzing
Block #93,227,716
14 transactions · 13 stateful · 2026-08-05 02:28:38 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,227,716 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w07w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x8eda8f35…062e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x59f95738…2d6d
0xe52b14…7230
3 touches
1 conflict
0x2999ebda…ce6c
0x34b655…2a6f
2 touches
0 conflicts
0x2b747f7d…4d32
0x34b655…2a6f
2 touches
0 conflicts
0x300890c0…aacf
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x109d8a5293…02a7b7
Audit this contract →
← previous block·next block →recent activity