← previous blocknext block →recent activity
Analyzing
Block #93,237,930
16 transactions · 14 stateful · 2026-08-05 03:19:59 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,237,930 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w27w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xfa551be3…a911
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x2eb7c3e4…fdd0
0xd32edf…ff58
3 touches
1 conflict
0x34920c68…3fac
0xa6afd3…d132
2 touches
1 conflict
0x9efe1c65…24dd
0xa6afd3…d132
2 touches
1 conflict
0xe2263bea…6aa0
0x2b46c0…1669
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
1 conflict on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity