← previous blocknext block →recent activity
Analyzing
Block #94,868,967
23 transactions · 23 stateful · 2026-08-10 20:19:57 UTC
Parallelism
74/100
Blocked
52%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,868,967 · 23 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
1w02w13w04w05w16w19w110w211w316w417w018w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004c
0x80c745…7210
12 touches
15 conflicts
0x00000000…004b
0x80c745…7210
12 touches
15 conflicts
0x216ffe66…1f94
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xeae24c…0be0
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0xac3e4969…39e9
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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: 0x80c74517…647210
15 conflicts on slot 0x0000000000…00004c
Audit this contract →
← previous block·next block →recent activity