← previous blocknext block →recent activity
Analyzing
Block #94,989,292
10 transactions · 9 stateful · 2026-08-11 06:25:06 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,989,292 · 10 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xb7184564…f86a
0x851145…3f07
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0x7e9ebc0e…9a72
0x851145…3f07
4 touches
1 conflict
0x3352fed8…8092
0x01bff4…1071
2 touches
0 conflicts
0xa8e98b9f…5935
0x01bff4…1071
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: 0x01bff417…bc1071
6 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity