← previous blocknext block →recent activity
Analyzing
Block #94,697,664
17 transactions · 14 stateful · 2026-08-10 05:56:46 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,697,664 · 17 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
1w02w16w07w09w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa86351b8…2c5a
0x34b655…2a6f
8 touches
6 conflicts
0x00d46156…3726
0x34b655…2a6f
4 touches
1 conflict
0x00dfe005…d032
0x34b655…2a6f
4 touches
1 conflict
0x0c0bcdfb…affe
0x34b655…2a6f
4 touches
1 conflict
0x0d461d23…e3fb
0x34b655…2a6f
4 touches
1 conflict
0x1d6ce97a…901b
0x34b655…2a6f
4 touches
1 conflict
0x2267f8c4…a571
0x34b655…2a6f
4 touches
1 conflict
0x23ef1567…8f31
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 0xa86351b861…d52c5a
Audit this contract →
← previous block·next block →recent activity