← previous blocknext block →recent activity
Analyzing
Block #94,201,747
13 transactions · 12 stateful · 2026-08-08 12:09:54 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,201,747 · 13 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
1w02w13w24w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
8 touches
6 conflicts
0x19e69334…a345
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x369883e3…a449
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x410b84ab…1dbc
0x34b655…2a6f
2 touches
0 conflicts
0x57b57f51…2449
0x34b655…2a6f
2 touches
0 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity