← previous blocknext block →recent activity
Analyzing
Block #93,674,878
16 transactions · 14 stateful · 2026-08-06 15:56:42 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,674,878 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w112w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f97aa17…6776
0x34b655…2a6f
4 touches
1 conflict
0xc6000ba5…8d65
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x10931b19…b748
0x34b655…2a6f
2 touches
0 conflicts
0x124a2fe8…2ea9
0x34b655…2a6f
2 touches
0 conflicts
0x334aa47d…cac0
0x34b655…2a6f
2 touches
0 conflicts
0x39c5ff72…c870
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 0x4f97aa17eb…2d6776
Audit this contract →
← previous block·next block →recent activity