← previous blocknext block →recent activity
Analyzing
Block #90,448,692
8 transactions · 6 stateful · 2026-07-26 09:23:28 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,448,692 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xa8c5904c…e1a7
0x34b655…2a6f
4 touches
1 conflict
0xb8746edd…bc38
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xec501e17…45fd
0x34b655…2a6f
4 touches
1 conflict
0x03bf1a82…9119
0x34b655…2a6f
2 touches
0 conflicts
0x05e1eba1…6491
0x34b655…2a6f
2 touches
0 conflicts
0x08b68583…01a1
0x34b655…2a6f
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity