← previous blocknext block →recent activity
Analyzing
Block #91,548,143
15 transactions · 11 stateful · 2026-07-30 05:37:51 UTC
Parallelism
87/100
Blocked
27%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,548,143 · 15 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
5w07w18w09w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x09a90ed3…6897
0x34b655…2a6f
2 touches
0 conflicts
0x0a6e6d8f…ab6c
0x34b655…2a6f
2 touches
0 conflicts
0x0cab691e…74a5
0x34b655…2a6f
2 touches
0 conflicts
0x0cc5cf9a…310d
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity