← previous blocknext block →recent activity
Analyzing
Block #93,464,721
17 transactions · 17 stateful · 2026-08-05 22:20:14 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,464,721 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w17w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9cd8eb0…09ae
0x34b655…2a6f
4 touches
1 conflict
0xe84a6c39…884f
0x34b655…2a6f
4 touches
1 conflict
0xfb67be15…a190
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x48c55262…944f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
1 conflict on slot 0xc9cd8eb023…a209ae
Audit this contract →
← previous block·next block →recent activity