← previous blocknext block →recent activity
Analyzing
Block #102,048,331
14 transactions · 13 stateful · 2026-09-05 00:56:44 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1.21
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,048,331 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w211w312w413w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb8288e3…7979
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x922cbc0c…51aa
0x34b655…2a6f
8 touches
6 conflicts
0x8d47c9a4…f11d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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
10 conflicts on slot 0xdb8288e38f…6f7979
Audit this contract →
← previous block·next block →recent activity