← previous blocknext block →recent activity
Analyzing
Block #93,063,719
19 transactions · 19 stateful · 2026-08-04 12:42:46 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,063,719 · 19 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
1w02w04w15w26w311w412w114w015w116w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3a621f8…75a2
0x34b655…2a6f
8 touches
6 conflicts
0xd6d06e7d…1f4b
0x34b655…2a6f
6 touches
3 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbc7d5199…c05f
0x34b655…2a6f
4 touches
1 conflict
0xbd41f53e…2dc4
0x34b655…2a6f
4 touches
1 conflict
0xc1d710e7…62ea
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
6 conflicts on slot 0xa3a621f8f3…6975a2
Audit this contract →
← previous block·next block →recent activity