← previous blocknext block →recent activity
Analyzing
Block #102,056,347
22 transactions · 20 stateful · 2026-09-05 01:37:21 UTC
Parallelism
73/100
Blocked
35%
Avg conflicts / tx
0.32
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,056,347 · 22 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
3w04w15w06w18w211w313w016w120w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1a9e7f0…12df
0x34b655…2a6f
4 touches
1 conflict
0xd36ed1d5…b4df
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x41c56387…a8f6
0x34b655…2a6f
4 touches
1 conflict
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
1 conflict on slot 0xd1a9e7f053…6412df
Audit this contract →
← previous block·next block →recent activity