← previous blocknext block →recent activity
Analyzing
Block #102,411,791
21 transactions · 19 stateful · 2026-09-06 07:38:43 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,411,791 · 21 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
1w02w14w05w17w19w214w315w417w218w519w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa918f7f0…f410
0x34b655…2a6f
8 touches
6 conflicts
0x0a6f5e37…6c3c
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf34802b3…9f10
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0xa918f7f04e…c9f410
Audit this contract →
← previous block·next block →recent activity