← previous blocknext block →recent activity
Analyzing
Block #90,793,564
19 transactions · 14 stateful · 2026-07-27 14:18:24 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,793,564 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w09w110w211w312w413w515w118w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48e3acd8…cf41
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xde945aa8…1ad5
0xa6afd3…d132
4 touches
1 conflict
0x7080a1d0…5104
0x34b655…2a6f
4 touches
1 conflict
0xd29e547b…a1dd
0x34b655…2a6f
4 touches
1 conflict
0xd93edb3f…94ec
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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 0x48e3acd863…7ecf41
Audit this contract →
← previous block·next block →recent activity