← previous blocknext block →recent activity
Analyzing
Block #93,291,423
11 transactions · 11 stateful · 2026-08-05 07:48:57 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,291,423 · 11 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
1w02w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56e54d0…2d39
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xd764b31d…aee3
0x34b655…2a6f
3 touches
1 conflict
0x28c180e1…f1e2
0x34b655…2a6f
2 touches
0 conflicts
0x5cc78005…4877
0x34b655…2a6f
2 touches
0 conflicts
0x82ae5c5e…4ccc
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 0xa56e54d018…f82d39
Audit this contract →
← previous block·next block →recent activity