← previous blocknext block →recent activity
Analyzing
Block #90,292,018
22 transactions · 18 stateful · 2026-07-25 20:01:42 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,292,018 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w18w09w110w211w312w415w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc6edb4d…ec54
0x0a2fbf…29b1
6 touches
3 conflicts
0xcc6edb4d…ec55
0x0a2fbf…29b1
6 touches
3 conflicts
0xcc6edb4d…ec56
0x0a2fbf…29b1
6 touches
3 conflicts
0xae27af1e…e9b2
0x0a2fbf…29b1
6 touches
3 conflicts
0xae27af1e…e9b3
0x0a2fbf…29b1
6 touches
3 conflicts
0xae27af1e…e9b6
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0005
0x370e2e…63b4
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
6 touches
3 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: 0x0a2fbf2d…f729b1
3 conflicts on slot 0xcc6edb4d0d…49ec54
Audit this contract →
← previous block·next block →recent activity