← previous blocknext block →recent activity
Analyzing
Block #93,537,671
21 transactions · 18 stateful · 2026-08-06 04:26:57 UTC
Parallelism
81/100
Blocked
56%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,537,671 · 21 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
2w03w14w05w17w08w19w212w013w114w216w217w318w319w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x424d48b2…e6ae
0x34b655…2a6f
6 touches
3 conflicts
0x428b6e5b…8909
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x264ddb78…fc48
0x34b655…2a6f
4 touches
1 conflict
0x26d8622c…e8af
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
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 0x424d48b260…92e6ae
Audit this contract →
← previous block·next block →recent activity