← previous blocknext block →recent activity
Analyzing
Block #102,519,394
16 transactions · 16 stateful · 2026-09-06 16:44:09 UTC
Parallelism
50/100
Blocked
56%
Avg conflicts / tx
0.94
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,519,394 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w38w49w411w313w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c6b3616…04cd
0x34b655…2a6f
8 touches
6 conflicts
0x20b94f7c…2a9b
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x083a8763…5a7d
0x1b6862…e19c
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 0x6c6b361647…6e04cd
Audit this contract →
← previous block·next block →recent activity