← previous blocknext block →recent activity
Analyzing
Block #93,490,745
21 transactions · 18 stateful · 2026-08-06 00:31:03 UTC
Parallelism
76/100
Blocked
28%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,490,745 · 21 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
1w04w05w18w29w312w113w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64f1eb47…cd27
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xe47f0750…4816
0x851145…3f07
4 touches
1 conflict
0x23a320fb…cbd7
0x34b655…2a6f
4 touches
1 conflict
0x34cdb3c2…96d2
0x34b655…2a6f
4 touches
1 conflict
0x428b6e5b…8909
0x34b655…2a6f
4 touches
1 conflict
0x7aae9795…06ed
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 0x64f1eb4791…95cd27
Audit this contract →
← previous block·next block →recent activity