← previous blocknext block →recent activity
Analyzing
Block #93,921,174
33 transactions · 23 stateful · 2026-08-07 12:35:22 UTC
Parallelism
85/100
Blocked
30%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,921,174 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w29w013w014w015w116w217w323w431w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd442ac37…1609
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x3cf50d44…961b
0x34b655…2a6f
6 touches
3 conflicts
0xa32723e2…ba91
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x2bbc0cfb…c2bc
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x5c16527f…628c
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
6 conflicts on slot 0xd442ac3711…dd1609
Audit this contract →
← previous block·next block →recent activity