← previous blocknext block →recent activity
Analyzing
Block #104,033,741
29 transactions · 24 stateful · 2026-09-12 00:05:55 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
1.28
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,033,741 · 29 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
1w02w13w24w35w46w58w011w012w113w215w316w417w520w623w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf30c163…0fb6
0x34b655…2a6f
14 touches
21 conflicts
0xfc8cd993…5c11
0x34b655…2a6f
14 touches
21 conflicts
0x3d3cb627…925e
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x2ae559ab…2904
0x34b655…2a6f
13 touches
21 conflicts
0x00000000…002b
0x1b6862…e19c
12 touches
15 conflicts
0xd1480c90…ae07
0x1b6862…e19c
12 touches
15 conflicts
0x7759d2f5…f4b7
0x34b655…2a6f
12 touches
15 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 0xaf30c16357…c70fb6
Audit this contract →
← previous block·next block →recent activity