← previous blocknext block →recent activity
Analyzing
Block #102,418,374
20 transactions · 15 stateful · 2026-09-06 08:12:05 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,418,374 · 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
2w03w18w09w114w215w318w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ca6aad8…502f
0x34b655…2a6f
8 touches
6 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x581b829b…9578
0x34b655…2a6f
4 touches
1 conflict
0x6d89ee77…72bf
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 0x2ca6aad88c…13502f
Audit this contract →
← previous block·next block →recent activity