← previous blocknext block →recent activity
Analyzing
Block #102,348,336
20 transactions · 18 stateful · 2026-09-06 02:17:18 UTC
Parallelism
65/100
Blocked
39%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,348,336 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w28w010w314w415w517w619w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x5150abbe…43c3
0x34b655…2a6f
6 touches
3 conflicts
0xe21a94dd…4838
0x34b655…2a6f
4 touches
1 conflict
0xfd4e632c…e14c
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x53c41998…7d52
0x34b655…2a6f
4 touches
1 conflict
0x0441269d…fc62
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity