← previous blocknext block →recent activity
Analyzing
Block #93,468,653
19 transactions · 17 stateful · 2026-08-05 22:40:00 UTC
Parallelism
58/100
Blocked
47%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,468,653 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w39w010w111w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
12 touches
15 conflicts
0x8d175439…fb79
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x63ee0193…a5b3
0x34b655…2a6f
8 touches
6 conflicts
0x50c0dd87…1128
0x34b655…2a6f
8 touches
6 conflicts
0x3260d0da…4385
0x34b655…2a6f
8 touches
6 conflicts
0xba9f9225…2ead
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity