← previous blocknext block →recent activity
Analyzing
Block #94,847,995
19 transactions · 18 stateful · 2026-08-10 18:34:28 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,847,995 · 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
1w02w13w04w15w07w110w211w112w313w414w515w117w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f46ea6…18c4
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
6 touches
3 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
6 touches
3 conflicts
0x5d2f2e75…e6b6
0x34b655…2a6f
4 touches
1 conflict
0x6b89ce6f…cc35
0x34b655…2a6f
4 touches
1 conflict
0x6c60fbcf…8744
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
10 conflicts on slot 0x63f46ea6ba…5318c4
Audit this contract →
← previous block·next block →recent activity