← previous blocknext block →recent activity
Analyzing
Block #94,681,494
19 transactions · 19 stateful · 2026-08-10 04:35:27 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,681,494 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w011w012w113w214w315w416w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x95e66f95…e987
0x34b655…2a6f
6 touches
3 conflicts
0x13202a25…0f5d
0x34b655…2a6f
6 touches
3 conflicts
0x27efc41a…dc7a
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x31519d10…f76b
0x34b655…2a6f
4 touches
1 conflict
0x34806510…f6e6
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity