← previous blocknext block →recent activity
Analyzing
Block #102,188,921
35 transactions · 30 stateful · 2026-09-05 12:49:34 UTC
Parallelism
66/100
Blocked
70%
Avg conflicts / tx
2.2
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #102,188,921 · 35 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w08w19w211w312w414w515w619w320w723w826w131w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x20b94f7c…2a9b
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xab2a87f1…eb01
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
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
36 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity