← previous blocknext block →recent activity
Analyzing
Block #100,122,334
18 transactions · 17 stateful · 2026-08-29 07:16:15 UTC
Parallelism
44/100
Blocked
65%
Avg conflicts / tx
2.44
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,122,334 · 18 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w27w38w410w511w612w713w814w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8a8db2…8a6d
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xec52192d…9919
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0xb9d94bb1…fc78
0x34b655…2a6f
5 touches
3 conflicts
0xfaf89f45…ced6
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
28 conflicts on slot 0x5c8a8db2ad…f58a6d
Audit this contract →
← previous block·next block →recent activity