← previous blocknext block →recent activity
Analyzing
Block #90,039,323
16 transactions · 15 stateful · 2026-07-24 22:44:19 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,039,323 · 16 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
2w03w14w08w09w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3d2d003…29d2
0x34b655…2a6f
4 touches
1 conflict
0xd83879b2…0bfb
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf2d8abfb…9cb6
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x02fd7a39…d106
0x34b655…2a6f
4 touches
1 conflict
0x226ae29a…2612
0x34b655…2a6f
4 touches
1 conflict
0x62ef187f…3b2c
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 0xc3d2d00347…c229d2
Audit this contract →
← previous block·next block →recent activity