← previous blocknext block →recent activity
Analyzing
Block #93,537,883
30 transactions · 27 stateful · 2026-08-06 04:28:01 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,537,883 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w118w221w022w123w225w226w327w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa86351b8…2c5a
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0x2a84297b…bfb4
0x34b655…2a6f
4 touches
1 conflict
0x57eff3b4…efba
0x34b655…2a6f
4 touches
1 conflict
0x0b19c7e3…f181
0x34b655…2a6f
4 touches
1 conflict
0x1caf0c05…15ce
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity