← previous blocknext block →recent activity
Analyzing
Block #93,464,082
21 transactions · 20 stateful · 2026-08-05 22:17:01 UTC
Parallelism
76/100
Blocked
30%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,464,082 · 21 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
1w04w05w17w18w09w111w215w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x428b6e5b…8909
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xeefb3ace…6fd9
0x34b655…2a6f
6 touches
3 conflicts
0x255c240f…a115
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x9a61d480…6b22
0x065c9d…c394
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
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 0x428b6e5b99…c18909
Audit this contract →
← previous block·next block →recent activity