← previous blocknext block →recent activity
Analyzing
Block #102,740,312
20 transactions · 20 stateful · 2026-09-07 11:19:38 UTC
Parallelism
65/100
Blocked
45%
Avg conflicts / tx
1.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,740,312 · 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
1w02w05w06w17w28w010w312w414w116w317w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x87a9e0cb…c05f
0x34b655…2a6f
8 touches
6 conflicts
0x014e90b3…470f
0x34b655…2a6f
8 touches
6 conflicts
0x03a4d625…a24e
0x34b655…2a6f
7 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity