← previous blocknext block →recent activity
Analyzing
Block #93,556,232
14 transactions · 14 stateful · 2026-08-06 06:00:15 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,556,232 · 14 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
1w02w13w25w06w17w18w09w010w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x33d4fbe3…a782
0x34b655…2a6f
6 touches
3 conflicts
0xb7fe0c60…1775
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x8d3e8f8c…8de4
0x34b655…2a6f
4 touches
1 conflict
0x947bb79d…6458
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
3 conflicts on slot 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity