← previous blocknext block →recent activity
Analyzing
Block #93,077,481
32 transactions · 27 stateful · 2026-08-04 13:52:31 UTC
Parallelism
88/100
Blocked
48%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,077,481 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w110w011w113w214w116w219w020w121w022w123w224w225w026w127w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb56f0740…7542
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x5581d709…ab77
0x2a68ba…90c5
6 touches
3 conflicts
0x4bc1abab…5874
0x34b655…2a6f
5 touches
3 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
4 touches
1 conflict
0xbc66586e…20fe
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 0xb56f0740e2…c17542
Audit this contract →
← previous block·next block →recent activity