← previous blocknext block →recent activity
Analyzing
Block #94,202,769
30 transactions · 30 stateful · 2026-08-08 12:15:05 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,202,769 · 30 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
1w02w13w14w223w224w326w329w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fafc50a…e3b0
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x9cd33a29…fef8
0x34b655…2a6f
4 touches
1 conflict
0x9d6946b4…7f4e
0x34b655…2a6f
4 touches
1 conflict
0xf9874e36…beed
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
6 conflicts on slot 0x7fafc50aa9…69e3b0
Audit this contract →
← previous block·next block →recent activity