← previous blocknext block →recent activity
Analyzing
Block #104,033,748
25 transactions · 25 stateful · 2026-09-12 00:05:57 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,033,748 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w110w011w112w213w314w415w516w617w720w222w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa24929f…7992
0x34b655…2a6f
16 touches
28 conflicts
0x07d94be1…7fa8
0x34b655…2a6f
16 touches
28 conflicts
0x33649c4f…b327
0x34b655…2a6f
16 touches
28 conflicts
0x3d3cb627…925e
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
16 touches
28 conflicts
0x7759d2f5…f4b7
0x34b655…2a6f
16 touches
28 conflicts
0xaf30c163…0fb6
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
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
28 conflicts on slot 0xfa24929f3c…597992
Audit this contract →
← previous block·next block →recent activity