← previous blocknext block →recent activity
Analyzing
Block #93,245,751
16 transactions · 15 stateful · 2026-08-05 03:59:18 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,245,751 · 16 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
1w02w06w17w28w19w311w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2385516f…eca5
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x13ec7d5d…792b
0x34b655…2a6f
4 touches
1 conflict
0x297e9342…3292
0x34b655…2a6f
4 touches
1 conflict
0x3546624c…cbe4
0x34b655…2a6f
4 touches
1 conflict
0x4a1261f9…46b8
0x34b655…2a6f
4 touches
1 conflict
0xfceb7edc…e1e7
0x34b655…2a6f
4 touches
1 conflict
0x048d51cb…6670
0x065c9d…c394
4 touches
1 conflict
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
15 conflicts on slot 0x2385516f6a…9aeca5
Audit this contract →
← previous block·next block →recent activity