← previous blocknext block →recent activity
Analyzing
Block #93,356,269
19 transactions · 17 stateful · 2026-08-05 13:14:58 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,356,269 · 19 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
1w02w13w04w06w07w18w19w210w011w112w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45ea7a97…bbb3
0x34b655…2a6f
10 touches
10 conflicts
0xac3e4969…39e9
0x34b655…2a6f
8 touches
6 conflicts
0xa558e115…fc88
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xebac0f82…a49c
0x34b655…2a6f
6 touches
3 conflicts
0x2dccba03…d655
0x34b655…2a6f
4 touches
1 conflict
0x3093e806…bde2
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
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
10 conflicts on slot 0x45ea7a9723…bdbbb3
Audit this contract →
← previous block·next block →recent activity