← previous blocknext block →recent activity
Analyzing
Block #102,094,059
16 transactions · 14 stateful · 2026-09-05 04:48:40 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,094,059 · 16 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
3w04w16w28w010w311w413w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1f4e6c86…7789
0x34b655…2a6f
6 touches
3 conflicts
0xbd5d2418…7cde
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x5ee5fdc2…74b9
0x34b655…2a6f
6 touches
3 conflicts
0xece8fecd…cc3a
0x34b655…2a6f
4 touches
1 conflict
0x25ec781a…dca9
0x34b655…2a6f
4 touches
1 conflict
0x953517cb…cdec
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity