← previous blocknext block →recent activity
Analyzing
Block #90,204,415
8 transactions · 8 stateful · 2026-07-25 12:39:24 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,204,415 · 8 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
1w02w14w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99701186…1cbf
0x34b655…2a6f
4 touches
1 conflict
0x9af03de8…05b0
0x34b655…2a6f
4 touches
1 conflict
0xaec054bf…ec66
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xe77c721b…7588
0x34b655…2a6f
4 touches
1 conflict
0xf4a9fd5e…88c9
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
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 0x997011860a…ad1cbf
Audit this contract →
← previous block·next block →recent activity