← previous blocknext block →recent activity
Analyzing
Block #102,175,074
20 transactions · 19 stateful · 2026-09-05 11:39:23 UTC
Parallelism
80/100
Blocked
26%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,175,074 · 20 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
6w07w112w013w114w015w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xffb2bfcf…b92a
0x34b655…2a6f
4 touches
1 conflict
0xf18de027…77e2
0x34b655…2a6f
4 touches
1 conflict
0xe1af7d74…7622
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x6e6a8155…9636
0x34b655…2a6f
4 touches
1 conflict
0x6ea1896c…e06f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity