← previous blocknext block →recent activity
Analyzing
Block #94,901,172
19 transactions · 19 stateful · 2026-08-10 23:01:55 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,901,172 · 19 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
2w03w14w05w26w17w28w39w013w216w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38bdc5d3…a632
0x34b655…2a6f
6 touches
3 conflicts
0xd30f9e74…d404
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x01a056f8…64e4
0x34b655…2a6f
4 touches
1 conflict
0x17aad0b2…59d0
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
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
3 conflicts on slot 0x38bdc5d3e1…01a632
Audit this contract →
← previous block·next block →recent activity