← previous blocknext block →recent activity
Analyzing
Block #93,563,755
70 transactions · 68 stateful · 2026-08-06 06:38:04 UTC
Parallelism
97/100
Blocked
4%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,563,755 · 70 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
1w03w04w16w07w08w167w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aae9795…06ed
0x34b655…2a6f
4 touches
1 conflict
0xd18e4cb7…88d4
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xfa32e465…6584
0xe52b14…7230
3 touches
1 conflict
0x88e771e8…7d4a
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 0x7aae979517…b606ed
Audit this contract →
← previous block·next block →recent activity