← previous blocknext block →recent activity
Analyzing
Block #93,537,594
15 transactions · 15 stateful · 2026-08-06 04:26:34 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,537,594 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w19w010w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b42f6a7…f49c
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
2 touches
0 conflicts
0x87292c3e…5e25
0x34b655…2a6f
2 touches
0 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x7b42f6a7e5…ebf49c
Audit this contract →
← previous block·next block →recent activity