← previous blocknext block →recent activity
Analyzing
Block #93,421,058
21 transactions · 18 stateful · 2026-08-05 18:40:44 UTC
Parallelism
81/100
Blocked
17%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,421,058 · 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
3w012w013w114w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8252706a…7ca5
0x34b655…2a6f
4 touches
1 conflict
0xcf7bbede…8ca1
0x34b655…2a6f
4 touches
1 conflict
0x5a19ef35…dc70
0x34b655…2a6f
4 touches
1 conflict
0x961da181…ed17
0x34b655…2a6f
3 touches
1 conflict
0x25eb7079…cb76
0x34b655…2a6f
2 touches
0 conflicts
0x42275259…6050
0x34b655…2a6f
2 touches
0 conflicts
0x56f53fc9…46c2
0x34b655…2a6f
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity