← previous blocknext block →recent activity
Analyzing
Block #104,867,909
15 transactions · 15 stateful · 2026-09-14 22:36:46 UTC
Parallelism
47/100
Blocked
53%
Avg conflicts / tx
1.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,867,909 · 15 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
2w03w14w25w36w47w58w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c68d10b…8386
0x34b655…2a6f
16 touches
28 conflicts
0x6e0f1dd3…db06
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xf51ec09c…b4a9
0x34b655…2a6f
10 touches
10 conflicts
0x43eeb6cb…aca3
0x34b655…2a6f
8 touches
6 conflicts
0x7504da64…542f
0x34b655…2a6f
6 touches
3 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
4 touches
1 conflict
0x4031b3d0…9908
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
28 conflicts on slot 0x7c68d10b83…628386
Audit this contract →
← previous block·next block →recent activity