← previous blocknext block →recent activity
Analyzing
Block #101,093,751
32 transactions · 25 stateful · 2026-09-01 16:48:16 UTC
Parallelism
88/100
Blocked
44%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,093,751 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w16w07w19w010w115w219w020w121w022w123w227w028w129w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xecf978b8…532e
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0xa0d3faac…ae01
0x754704…b603
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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