← previous blocknext block →recent activity
Analyzing
Block #93,464,031
16 transactions · 14 stateful · 2026-08-05 22:16:46 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,464,031 · 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
4w05w19w112w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x706169e5…8f5c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xfcdb5918…2b49
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x7cc5cc1a…e1ce
0x065c9d…c394
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 0x706169e5b2…a88f5c
Audit this contract →
← previous block·next block →recent activity