← previous blocknext block →recent activity
Analyzing
Block #93,484,902
19 transactions · 16 stateful · 2026-08-06 00:01:41 UTC
Parallelism
74/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,484,902 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w17w210w311w012w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1b58b33…874f
0x34b655…2a6f
6 touches
3 conflicts
0xc6000ba5…8d65
0x34b655…2a6f
6 touches
3 conflicts
0xe21234e7…bded
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x80927d7d…58a7
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 0xb1b58b3385…e4874f
Audit this contract →
← previous block·next block →recent activity