← previous blocknext block →recent activity
Analyzing
Block #102,096,072
11 transactions · 11 stateful · 2026-09-05 04:58:52 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,096,072 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1513b999…b52e
0x34b655…2a6f
4 touches
1 conflict
0x26c599c1…706c
0x34b655…2a6f
4 touches
1 conflict
0x3774a68c…11ff
0x34b655…2a6f
4 touches
1 conflict
0x4a92f0b0…3dba
0x34b655…2a6f
4 touches
1 conflict
0x4b024b98…8f37
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x65f011a5…bc6e
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 0x1513b999be…b2b52e
Audit this contract →
← previous block·next block →recent activity